MCP Hub

What is MCP Hub?

MCP Hub is a central coordinator that connects clients to multiple MCP servers, providing a single interface to utilize tools, resources, and prompts from those servers. It implements the MCP 2025-03-26 specification and is designed for developers who need to manage and interact with multiple MCP servers from one endpoint.

How to use MCP Hub?

Install globally via npm (npm install -g mcp-hub) and start the hub server with mcp-hub --port 3000 --config path/to/config.json. Configure managed servers in a JSON file under mcpServers, supporting STDIO and remote (streamable-http/SSE) servers.

Key features of MCP Hub

• Dynamic server management: start, stop, enable/disable servers on demand
• Unified REST API to execute tools and access resources
• Real-time server status and capability updates via SSE
• OAuth 2.0 with PKCE and header-based authentication
• Marketplace integration for server discovery and auto configuration
• Hot reload development mode for local servers

Use cases of MCP Hub

• Coordinate multiple MCP servers from a single client endpoint
• Build editor plugins (e.g., Neovim) that call MCP tools and resources
• Manage local and remote MCP servers with health monitoring and auto-reconnection
• Expose a REST API to external applications that need MCP capabilities
• Automate server lifecycle (start/stop/refresh) via API calls

FAQ from MCP Hub

What transports does MCP Hub support?

MCP Hub supports streamable-http, SSE, and STDIO transports.

Does MCP Hub support OAuth authentication?

Yes, it supports OAuth 2.0 with PKCE flow and header-based tokens.

How does MCP Hub handle server reconnection?

It includes automatic reconnection with backoff and health monitoring for connected servers.

Can I use MCP Hub with local and remote servers?

Yes, it supports local STDIO servers and remote servers using streamable-http or SSE.

Does MCP Hub support roots, sampling, or completion?

No, these MCP capabilities are not supported.