mcp -manager

MCP Server Manager provides a web-based GUI to configure and manage multiple MCP clients across different servers. It exposes a single configuration surface that translates to the appropriate client configurations (files) so you don’t have to edit JSON files by hand. The built-in web interface runs locally on http://localhost:6543 and includes real-time validation to catch misconfigurations before you deploy. You can enable, disable, or modify individual MCP server entries per client from the GUI, and changes are automatically synchronized to the target client configurations.

Prerequisites:

• A supported OS (Linux, macOS, Windows)
• Internet access to download/install binaries

Option 1: Debian/Ubuntu Package (Recommended)

# Download the latest .deb from GitHub Releases
wget https://github.com/vlazic/mcp-server-manager/releases/latest/download/mcp-server-manager_Linux_x86_64.deb

# Install the package
sudo dpkg -i mcp-server-manager_Linux_x86_64.deb

# Enable and start the service
systemctl --user enable --now mcp-server-manager

Option 2: Download Release Binary

# Download and extract
wget https://github.com/vlazic/mcp-server-manager/releases/latest/download/mcp-server-manager_Linux_x86_64.tar.gz
tar -xzf mcp-server-manager_Linux_x86_64.tar.gz
chmod +x mcp-server-manager

# Run directly (config will be auto-created)
./mcp-server-manager

# Or specify custom config location
./mcp-server-manager --config /path/to/config.yaml
./mcp-server-manager -c /path/to/config.yaml

Option 3: Build from Source

git clone https://github.com/vlazic/mcp-server-manager.git
cd mcp-server-manager

# Build only
make build

# Build, install, and start as system service
make setup

Tips and notes:

• The manager supports multiple MCP transports (e.g., filesystem/command-based, HTTP-based with URLs) and multiple MCP clients. Use the web UI to add or modify servers and then assign them to clients in the config.
• Config file locations are resolved in this order: command line flag, user config at ~/.config/mcp-server-manager/config.yaml, current directory ./config.yaml, or embedded defaults.
• On first run, a default config is created at ~/.config/mcp-server-manager/config.yaml. Edit it or use the web UI to customize.
• Ensure the required commands are in PATH (e.g., npx). If a server does not start, check the logs for path or syntax errors.
• The GUI is served at http://localhost:6543. If port conflicts occur, change the port in your config or command line if supported by your build.
• For the HTTP transports, keep your API keys secret and consider restricting access to trusted clients/IPs.
• When using the filesystem transport, provide a valid directory path and the necessary permissions for the process to read/write as needed.