mcp-hub
by ravitemer·★ 487·Score 49
A centralized hub for managing multiple MCP servers with unified endpoints and dynamic server monitoring.
Overview
MCP Hub acts as a central coordinator for MCP servers and clients, providing two key interfaces: a management interface through a REST API and web UI, and an MCP server interface that allows clients to access all server capabilities through a single endpoint. It implements the MCP 2025-03-26 specification and supports various transport protocols including streamable-http, SSE, and STDIO for local and remote servers. The hub automatically namespaces capabilities to prevent conflicts, routes requests to appropriate servers, and handles authentication with OAuth 2.0 and header-based tokens.
Try asking AI
After installing, here are 5 things you can ask your AI assistant:
When to choose this
Choose MCP Hub when you need to manage multiple MCP servers with a centralized interface and want to simplify client connections through a single endpoint.
When NOT to choose this
Avoid MCP Hub if you're running a simple setup with only one MCP server, as it adds unnecessary complexity for basic use cases.
Comparable tools
Installation
npm install -g mcp-hubStart the hub server:
mcp-hub --port 3000 --config path/to/config.jsonClaude Desktop configuration:
{
"mcpServers": {
"Hub": {
"url": "http://localhost:37373/mcp"
}
}
}FAQ
- What MCP capabilities are supported?
- MCP Hub supports Tools, Resources, Resource Templates, and Prompts with real-time updates. It does not currently support Roots, Sampling, or Completion capabilities.
- How does authentication work?
- The hub supports OAuth 2.0 with PKCE flow and header-based token authentication for remote servers. Local STDIO servers can use environment variables with placeholder resolution.
Compare mcp-hub with
Last updated · Auto-generated from public README + GitHub signals.