Skip to main content

mc-man

The Minecraft server jar and plugin manager, downloader and updater

mc-man is a terminal program for managing server jars and plugins for Minecraft servers. It is created with simplicity in mind, and aims to be the difinitive tool to use for server maintaince, for example when updating a server. mc-man can download and update spigot, craftbukkit, mcpc+, bungeecord and the mojang server. It can also download and update plugins, with regards to dependencies. With one command you can update all your plugins. There is also features to export and import servers. They work by saving references to all plugins and server jars in a json-file, which can later be used to recreate the server.

Features

  • Update all plugins with one command

  • Download plugins with dependency resolution

  • All downloads are checked with checksum

  • Download and update server jars.

Installing

mc-man is programmed in Python for Linux. It can only run on Python 3.3 or newer. This might be a problem on some Linux distributions, but it should always be possible to build Python from source, if it is not present in your package manager. Together with python you need the python header files, which you normally can get through a package called something like python3-dev. In addition to python you are recommended to have pip - the Python package manager. Once you have Python 3.3 or newer, and pip for your version of Python, you can run this command to install mc-man:

sudo pip3.3 install mc-man

If you are running Python 3.4, pip3.3 should be replaced with pip3.4. If neither of those commands exists, you can try pip3, but you have to verify that it leads to a pip version for Python 3.3 or newer.

mc-man has some dependencies which will be installed automatically when installing using pip:

  • PyYaml - For parsing the yaml files in plugins

  • pyBukGet - For access to the BukGet API

  • pySpaceGDN - For access to the SpaceGDN API

If you install mc-man without pip, you will have to install these dependencies manually.

Usage

The base command for mc-man is mcman, all of mc-man’s functionality is accessable through that command. The command is expected to be run from the root folder of the server. The functionality is divided into four sub commands:

server

The server command is used for managing server jars. It can be used to find versions and builds, identify jars existing locally and downloading new jars.

plugin

The plugin command is used for managing plugins. It can be used to search for plugins, display info about them and their versions, list downloaded plugins and check which of them are out of date, update the plugins and, of course, download new plugins.

export

The export command is used for exporting the servers state. It will find all downloaded servers and plugins and save their placement, relative to the server root, and their versions to a json file. This file can later be used by the import command to create a new server with the same server version and plugins.

import

The import command is used for importing a previously exported server state. It will recreate a server with the info from the json file it is passed.

These commands can be called with mcman <command>, to manage plugins for example: mcman plugin. The commands can also be shortened to the first letter: mcman p. In addition to this comprehensive documentation, a lighter documentation is included in the program, it can be accessed by adding --help at the end of any command or subcommand, for example: mcman p --help, to get quick help for the plugin command.’

Often used commands

Here are some commands that are used often:

mcman p download <plugin> [<plugin> ...]

Download the plugins.

mcman p update

To update all the plugins

mcman p list

To list the installed plugins, and check if any are out of date.

mcman s identify <server.jar>

To check what version and build a server jar is, and see if there are any updates to it.

mcman s download <server> [<channel>] [<version>] [<build>]

To download a server, optionally a version from the specified channel, the specified version, or even a specific build.

Metadata

Release files for mc-man 0.9-1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mc-man 0.9-1
File Size Uploaded Provenance Actions
mc-man-0.9-1.tar.gz 22.2 kB Without provenance Details for mc-man-0.9-1.tar.gz

Release files / mc-man-0.9-1.tar.gz

Download URL mc-man-0.9-1.tar.gz
Size 22.2 kB
Tags Source
SHA-256 checksum
How to use checksums
1a086e544e309c30fa775bee0d0abf31b5d1b3cb63fe3196dd0e0dadf1972e6f
BLAKE2b-256 checksum
How to use checksums
d1f7012f373a190656a37f6d90b82e7af450b967c026229c2e8d29a2cdbc25e1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for mc-man 0.9-1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page