MCP Hub

What is MCP Hub?

MCP Hub is a central coordinator for MCP servers and clients that provides a unified REST API and web UI for managing multiple servers and a single MCP endpoint (/mcp) that any MCP client can connect to access all server capabilities. It implements the MCP 2025-03-26 specification and is designed for developers who need to manage and aggregate multiple MCP servers under one interface.

How to use MCP Hub?

Install globally with npm install -g mcp-hub, then start with mcp-hub --port 3000 --config path/to/config.json. Configure any MCP client (e.g., Claude Desktop) to use a single endpoint http://localhost:37373/mcp instead of separate entries for each server.

Key features of MCP Hub

• Centralized management via REST API and web UI
• Single MCP endpoint for all clients
• Supports STDIO, streamable-http, and SSE transports
• Real-time server status and capability updates
• OAuth 2.0 authentication with PKCE flow
• Direct use of VS Code .vscode/mcp.json configs

Use cases of MCP Hub

• Aggregate multiple MCP servers behind one endpoint for any compliant client
• Manage server lifecycle (start/stop/enable/disable) through a unified interface
• Develop MCP servers with hot reload using dev mode and file watching
• Migrate existing VS Code MCP configurations seamlessly to a centralized hub

FAQ from MCP Hub

What transports does MCP Hub support?

MCP Hub supports STDIO for local script-based servers and streamable-http/SSE for remote servers.

Can MCP Hub use existing VS Code MCP configuration files?

Yes, it supports both mcpServers and servers keys and VS Code variable substitution (${env:}, ${input:}, predefined variables), so .vscode/mcp.json files work directly.

How does MCP Hub handle authentication?

It supports OAuth 2.0 with PKCE flow and header-based token authentication for remote servers.

Does MCP Hub support all MCP capabilities?

It fully supports Tools, Resources, Resource Templates, and Prompts with real‑time updates. Roots, Sampling, and Completion are not supported.

How can I provide input variables for VS Code compatibility?

Use the MCP_HUB_ENV environment variable as a JSON string containing key-value pairs for ${input:variable-id} placeholders.