Summary
One endpoint for every client, and server management moves out of JSON files.
The payoff is not just fewer config entries: because the hub holds the connections, you can turn a server off or restart it without touching any client, and capability changes propagate live. VS Code config files work as-is, so migrating is mostly pointing it at the file you already have.
What it is
A hub that connects to many MCP servers and re-exposes all of them through a single endpoint, plus a REST API and web UI for managing those servers.
What you get
- One URL for clients to connect to — localhost:37373/mcp — instead of one entry per server
- Capabilities from every managed server, namespaced so two servers can both have a tool called search
- Start, stop, enable and disable managed servers on demand, with health monitoring and reconnection
- Local STDIO servers and remote streamable-http or SSE servers side by side, with OAuth 2.0 PKCE and header auth
- Live updates when a server's tool, resource or prompt list changes
- Hot reload — a managed server restarts on file changes in dev mode
Requirements
Npm install -g mcp-hub, then start it with a port and at least one config file. It reads the same JSON your clients use, including VS Code's .vscode/mcp.json with servers, ${env:} and ${input:} syntax; multiple config files merge in order.
Setup effort
One command — npm install -g mcp-hub