Skip to content
Voltar ao Blog
Terminal window showing mcman CLI commands for Minecraft server configuration and plugin management

Mcman: Manage Your Minecraft Server Like Code in 2026

ice
ice
@ice
Updated
18 visualizações
TL;DR:Mcman is a command-line Minecraft Server Manager that treats your server setup like code - with git version control, automatic plugin downloads, and reproducible deployments. Perfect for admins managing servers, networks, or testing custom configurations.

" Powerful Minecraft Server Manager CLI. Easily install jars (server, plugins & mods) and write config files. Docker and git support included."

deniz-blue/mcman · github.com
⭐ 304 stars💻 Rust📜 GPL-3.0

Tired of manually downloading plugins, hunting for the right server version, and crossing your fingers that your mod list doesn't break? Mcman treats your Minecraft server like a code repository - everything in one config file, automatic downloads, git-friendly, and surprisingly efficient.

What This Project Does

Mcman is a command-line tool written in Rust that handles the tedious parts of running a Minecraft server. Instead of hunting links, copy-pasting JAR files, and manually editing config files, you describe what you want in a single server.toml file - your server version, plugins, mods, configurations - and mcman handles the rest. It downloads everything, verifies file integrity, and keeps things organized.

The magic part? You can version control this entire setup with git. Add a plugin, update your TOML, commit it, push it. Your teammates can pull the changes and mcman will fetch everything they need. No more "wait, what version of X are we using?" confusion.

(Actually, this works for managing whole networks too with a network.toml if you're running multiple servers.)


Why You'd Use This

First, there's the obvious case: if you're running a custom server network, Mcman saves ridiculous amounts of time. I've seen server admins spend hours managing plugin versions across 5+ servers. Mcman cuts that down to a few commands. Update once, deploy everywhere.

But there's a subtler reason. If you're testing different plugin combinations or experimenting with new modpack setups, Mcman lets you branch, experiment, and roll back cleanly - just like code development. Your main branch stays stable while you test features on a development branch before merging.

You'll also appreciate this if you've ever wanted to share a server setup with a friend or colleague. Send them the repo, they run mcman run, and they've got your exact configuration. No more "wait, did you use CraftBukkit or Spigot?" arguments.


Getting Started with Installation

Getting mcman running is straightforward. On Linux and macOS, just grab the latest binary from releases:

bash
curl -L https://github.com/deniz-blue/mcman/releases/download/0.4.5/mcman -o mcman
chmod +x mcman./mcman - version

Windows users can either grab the .exe from the releases page, or use Scoop if you've got it set up:

powershell
scoop bucket add minecraft https://github.com/The-Simples/scoop-minecraft
scoop install mcman

Linux users on Arch can install from AUR with yay -S mcman-bin or paru -S mcman-bin. Once installed, you initialize a new server:

bash
mcman init

This walks you through creating your server.toml - pick your Minecraft version, server type (Paper, Spigot, Purpur, etc.), and you're rolling. Then mcman run starts your server, and mcman dev is the interesting one - it watches for changes and hot-reloads your server without full restarts.


What Makes This Stand Out

Actual config file support. Most server managers download the JAR and hope you figure out the rest. Mcman lets you manage server.properties, plugins' YAML files, and custom configs all in one place, with variable substitution. Change one setting across 10 files? You're not copy-pasting into each one.

GitHub project card for deniz-blue/mcman
GitHub project card for deniz-blue/mcman

Works with nearly every source. Modrinth, CurseForge, Hangar, Spigot, GitHub releases, Jenkins, Maven repositories - if a plugin or mod lives there, mcman can pull it. Need something custom? Just throw in a direct URL.

Docker ready. Building a containerized Minecraft setup? Mcman plays nice with Docker containers. Generate a Dockerfile, use mcman inside it, ship it out.

Git integration that actually works. This isn't just "oh you can version control your configs" - it's properly thought through. Worlds stay as zips in worlds/, plugins are locked to specific versions in the manifest, everything is reproducible. And if you need to fine-tune your server settings, our Server Properties Generator makes that process faster.

The project sits at 304 stars on GitHub and is actively maintained. Rust performance means it's actually fast, which matters when you're managing multiple servers.


Things to Watch Out For

One thing that catches people: the rewrite happening on the v2 branch is substantial. If you're deploying something for a community, stick with the stable 0.4.5 release. Check the Discord (linked on the repo) for updates on v2 progress before committing to it.

Config variables are powerful but require you to actually write them correctly.

Typos won't always fail loudly - you'll just get weird behavior at runtime. Read the docs on variable syntax before you get frustrated. Also, if you're setting up shared servers, remember that Mcman's strength is in reproducibility - but that means everyone on the team needs to understand TOML syntax and git basics. It's not a GUI tool.

One more caveat: I'd recommend using this for server management workflow, not as a complete hosting solution. Mcman handles the setup and deployment bits beautifully, but you still need your own server hardware, hosting, or custom Docker orchestration. For calculating how to properly organize your world coordinates (especially if you're working across dimensions), check our Nether Portal Calculator.


Other Tools and Approaches

There are other paths if Mcman doesn't fit your needs. Paper's plugin ecosystem handles some of these problems, but it's more limited in scope - no git workflow. Docker has its own learning curve but works well for container-first teams. Hosting platforms handle deployment for you, though you lose flexibility.

Mcman sits in a nice middle ground: powerful enough for serious server operations, simple enough that one admin can handle it, and flexible enough to scale up.


What's The Verdict

Mcman isn't flashy. It's a command-line tool that makes running Minecraft servers boring in the best way possible - you spend your time building worlds and running your community, not wrestling with configuration files.

If you're currently managing Minecraft servers and copying files around manually, this is worth thirty minutes of your time to evaluate.

The project's on GitHub, the documentation is solid, and the Discord is active if you get stuck.

Frequently Asked Questions

Is Mcman free and open source?
Yes, Mcman is completely free and released under the GPL-3.0 license. The source code is available on GitHub, and you can compile it yourself or use pre-built binaries for Windows, macOS, and Linux. No licensing fees or proprietary restrictions.
What Minecraft server types does Mcman support?
Mcman supports Paper, Spigot, Purpur, Folia, and other popular Java server implementations. It also handles Fabric and Forge mod loaders, plus plugin managers from sources like Modrinth, Hangar, CurseForge, and Spigot. Custom JAR URLs work too if you need something specific.
Can I use Mcman if I'm not familiar with git?
You'll find it much easier with basic git knowledge (clone, commit, push), but it's not absolutely required. Mcman's core features work fine with just command-line usage. However, the main advantage - version control and easy sharing - requires understanding git. Learning basics takes a few hours.
Does Mcman work with modpacks like Technic or CurseForge?
Mcman can import from and export to Modrinth packs and packwiz formats, giving you compatibility with many modpack ecosystems. For Technic-specific packs, you'd need to manually configure them in your server.toml, but it's straightforward since you list mods individually.
What happens if my server setup breaks after an update?
Git is your safety net - simply revert to a previous commit with `git checkout`. Mcman will then fetch the exact same versions of plugins and mods you had before. This rollback capability is one of the biggest advantages over manual management.