MCP-manager

MCP Manager provides a centralized control plane for multiple MCP servers. It can automatically discover and install backend MCP servers from sources like NPM, GitHub, or local paths, route requests between clients and servers, and enforce per-client access rules. Use the manager to start, monitor, and configure all managed MCP servers from a single YAML file. Clients (such as VSCode MCP Extension or Claude Desktop) connect to the manager rather than to individual MCP servers, simplifying authentication and permission management. The manager exposes tooling to start, stop, install, validate configurations, and inspect permissions, making it easier to maintain secure and scalable MCP environments.

Prerequisites:

• Python 3.8+ and pip
• Access to install pip dependencies

Install the MCP Manager from source:

1. Clone the repository or download the source code.
2. Install dependencies in editable mode (as recommended in the README):

cd MCP-manager
pip install -e .

Alternative (if you prefer to run via CLI directly):

cd MCP-manager
uv sync

Create and customize your configuration:

cp mcp-manager.example.yaml mcp-manager.yaml
# Edit mcp-manager.yaml to configure your servers, clients, sources, and runtime options

Run the MCP Manager:

python main.py mcp-manager.yaml
# or using the CLI (if available in your environment)
mcp-manager start --config mcp-manager.yaml

Verify installation and configuration:

mcp-manager config validate
mcp-manager config show

Notes and tips:

• This MCP Manager is described as archived in the README; prefer running via Docker if available to simplify deployments and isolation.
• The configuration supports automatic installation of backend MCP servers from NPM, GitHub, or local paths. Ensure your sources are reachable and tokens (NPM/GitHub) are set if required.
• Environment variables such as WEATHER_API_KEY and DATABASE_URL may be needed by certain servers; keep them in sync with your actual backend requirements.
• If you encounter access issues, review client permissions with the provided CLI commands (e.g., mcp-manager client permissions <client_id>). Use config validate to catch syntax or schema problems early.
• For production, consider running behind a reverse proxy, enabling health checks, and tuning cache and concurrency settings in runtime configuration.