MCP Hub acts as a central coordinator for MCP servers and clients, providing two key interfaces:
How to install mcp-hub?
ravitemer/mcp-hub
$git clone https://github.com/ravitemer/mcp-hubInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install mcp-hub by running `git clone https://github.com/ravitemer/mcp-hub`, then use it for the current task and follow its documentation at https://github.com/ravitemer/mcp-hub.
README.md
| 1 | # MCP Hub |
| 2 | |
| 3 | [](https://www.npmjs.com/package/mcp-hub) |
| 4 | [](https://opensource.org/licenses/MIT) |
| 5 | [](./CONTRIBUTING.md) |
| 6 | |
| 7 | MCP Hub acts as a central coordinator for MCP servers and clients, providing two key interfaces: |
| 8 | |
| 9 | 1. **Management Interface** (/api/*): Manage multiple MCP servers through a unified REST API and web UI |
| 10 | 2. **MCP Server Interface** (/mcp): Connect ANY MCP client to access ALL server capabilities through a single endpoint |
| 11 | |
| 12 | This dual-interface approach means you can manage servers through the Hub's UI while MCP clients (Claude Desktop, Cline, etc.) only need to connect to one endpoint (`localhost:37373/mcp`) to access all capabilities. Implements [MCP 2025-03-26](https://modelcontextprotocol.io/specification/2025-03-26) specification. |
| 13 | |
| 14 | ## Feature Support |
| 15 | |
| 16 | | Category | Feature | Support | Notes | |
| 17 | |----------|---------|---------|-------| |
| 18 | | **Transport** |||| |
| 19 | | | streamable-http | ✅ | Primary transport protocol for remote servers | |
| 20 | | | SSE | ✅ | Fallback transport for remote servers | |
| 21 | | | STDIO | ✅ | For running local servers | |
| 22 | | **Authentication** |||| |
| 23 | | | OAuth 2.0 | ✅ | With PKCE flow | |
| 24 | | | Headers | ✅ | For API keys/tokens | |
| 25 | | **Capabilities** |||| |
| 26 | | | Tools | ✅ | List tools | |
| 27 | | | 🔔 Tool List Changed | ✅ | Real-time updates | |
| 28 | | | Resources | ✅ | Full support | |
| 29 | | | 🔔 Resource List Changed | ✅ | Real-time updates | |
| 30 | | | Resource Templates | ✅ | URI templates | |
| 31 | | | Prompts | ✅ | Full support | |
| 32 | | | 🔔 Prompts List Changed | ✅ | Real-time updates | |
| 33 | | | Roots | ❌ | Not supported | |
| 34 | | | Sampling | ❌ | Not supported | |
| 35 | | | Completion | ❌ | Not supported | |
| 36 | | **Marketplace** |||| |
| 37 | | | Server Discovery | ✅ | Browse available servers | |
| 38 | | | Installation | ✅ | Auto configuration | |
| 39 | | **Real-time** |||| |
| 40 | | | Status Updates | ✅ | Server & connection state | |
| 41 | | | Capability Updates | ✅ | Automatic refresh | |
| 42 | | | Event Streaming to clients | ✅ | SSE-based | |
| 43 | | | Auto Reconnection | ✅ | With backoff | |
| 44 | | **Development** |||| |
| 45 | | | Hot Reload | ✅ | Auto restart a MCP server on file changes with `dev` mode | |
| 46 | | **Configuration** |||| |
| 47 | | | `${}` Syntax | ✅ | Environment variables and command execution across all fields | |
| 48 | | | VS Code Compatibility | ✅ | Support for `servers` key, `${env:}`, `${input:}`, predefined variables | |
| 49 | | | JSON5 Support | ✅ | Comments and trailing commas in configuration files | |
| 50 | |
| 51 | ## Simplified Client Configuration |
| 52 | |
| 53 | Configure all MCP clients with just one endpoint: |
| 54 | ```json |
| 55 | { |
| 56 | "mcpServers" : { |
| 57 | "Hub": { |
| 58 | "url" : "http://localhost:37373/mcp" |
| 59 | } |
| 60 | } |
| 61 | } |
| 62 | ``` |
| 63 | |
| 64 | The Hub automatically: |
| 65 | - Namespaces capabilities to prevent conflicts (e.g., `filesystem__search` vs `database__search`) |
| 66 | - Routes requests to the appropriate server |
| 67 | - Updates capabilities in real-time when servers are added/removed |
| 68 | - Handles authentication and connection management |
| 69 | |
| 70 | ## Key Features |
| 71 | |
| 72 | - **Unified MCP Server Endpoint** (/mcp): |
| 73 | - Single endpoint for ALL MCP clients to connect to |
| 74 | - Access capabilities from all managed servers through one connection |
| 75 | - Automatic namespacing prevents conflicts between servers |
| 76 | - Real-time capability updates when servers change |
| 77 | - Simplified client configuration - just one endpoint instead of many |
| 78 | |
| 79 | - **Dynamic Server Management**: |
| 80 | - Start, stop, enable/disable servers on demand |
| 81 | - Real-time configuration updates with automatic server reconnection |
| 82 | - Support for local (STDIO) and remote (streamable-http/SSE) MCP servers |
| 83 | - Health monitoring and automatic recovery |
| 84 | - OAuth authentication with PKCE flow |
| 85 | - Header-based token authentication |
| 86 | |
| 87 | - **Unified REST API**: |
| 88 | - Execute tools from any connected server |
| 89 | - Access resources and resource templates |
| 90 | - Real-time status updates via Server-Sent Events (SSE) |
| 91 | - Full CRUD operations for server management |
| 92 | |
| 93 | - **Real-time Events & Monitoring**: |
| 94 | - Live serv |
Related
6 picksType
- langchain-mcp-adaptersMake Anthropic Model Context Protocol (MCP) tools compatible with LangChain and LangGraph agents.Jul 2026
- mcporterTypeScript runtime and CLI for connecting to configured Model Context Protocol servers.Jul 2026
- mcp-proxyA MCP server which proxies requests to a remote MCP server over streamable HTTP or SSE.Jul 2026
- mcp-atlassianThe Model Context Protocol (MCP) Atlassian integration is an open-source implementation that bridges Atlassian products (Jira and Confluence) with AI language models following Anthropic's MCP specification.Jul 2026
- open-webuiOpen WebUIJul 2026
- rulesyncUnified AI rules management CLI tool that generates configuration files for various AI development toolsJul 2026
