mcp-serverman: A MCP Server Configuration Manager

A command-line tool to manage Claude MCP servers configuration with version control and profiling.

Warning

This tool is still in development and may not be stable and subject to changes.

Important

I always recommend making a manual backup of the mcp configuration before making any changes. Although I tried to cover some error handling in the code, it is definitely not inclusive.

💾Installation

pip install mcp-serverman 

or from GitHub for the latest debug version:

pip install git+https://github.com/benhaotang/mcp-serverman.git

Should be available on Windows, Linux(tested) and MacOS. If the path for a certain platform is wrong, open an issue.

💻Usage

After installation, you can use the mcp-serverman command directly in terminal:

# Display help message
mcp-serverman
# Initialize Client configuration(one time and must be done before using other commands, since 0.1.9)
mcp-serverman client init
# List servers
mcp-serverman list
mcp-serverman list --enabled
# Enable/disable/remove server/server version
mcp-serverman enable <server_name> 
mcp-serverman disable <server_name>
mcp-serverman remove <server_name>
# Version control
mcp-serverman save <server_name> --comment <comment>
mcp-serverman change <server_name> --version <version>
# Preset/Profile management
mcp-serverman preset save <preset_name>
mcp-serverman preset load <preset_name>
mcp-serverman preset delete <preset_name>
# Multiple client support(since 0.1.9)
mcp-serverman client list
mcp-serverman client add <short_name> --name "Display Name" --path "/path/to/config.json" --key "mcpServers" [--default]
mcp-serverman client remove <short_name>
mcp-serverman client modify <short_name> --default
mcp-serverman client copy --from <short_name> --to <short_name> --merge

For detailed usage instructions, see the manual.

🔧Development

To install the package in development mode, clone the repository and run:

pip install -e .

🏁Roadmap

• Add support for other MCP-Clients, e.g. Cline and MCP-Bridge (since 0.1.9)
• Update the code to be more modular and easier to maintain (since v0.2.0)
• Integration with other MCP server install tools, e.g. Smithery, or with predefined installation templates (should iron out safety issues first)
  • Define a template format for server installation and only allow git clone, npm install, pip install(virtual env first) via the template
  • Test with official servers
  • Add Smithery as one of allowed installation tools
  • Somehow to have a check update function? (help wanted)
• Better error handling tests
• Maybe a Web UI via Flask?

License

MIT License (LICENSE)