ravitemer/mcp-hub

MCP Hub acts as a central coordinator for MCP servers and clients, providing two key interfaces:
1. Management Interface (/api/): Manage multiple MCP servers through a unified REST API and web UI
2. MCP Server Interface (/mcp): Connect ANY MCP client to access ALL server capabilities through a single endpoint
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 specification.
## Feature Support
| Category | Feature | Support | Notes |
| Transport ||||
| | streamable-http | ✅ | Primary transport protocol for remote servers |
| | SSE | ✅ | Fallback transport for remote servers |
| | STDIO | ✅ | For running local servers |
| Authentication ||||
| | OAuth 2.0 | ✅ | With PKCE flow |
| | Headers | ✅ | For API keys/tokens |
| Capabilities ||||
| | Tools | ✅ | List tools |
| | 🔔 Tool List Changed | ✅ | Real-time updates |
| | Resources | ✅ | Full support |
| | 🔔 Resource List Changed | ✅ | Real-time updates |
| | Resource Templates | ✅ | URI templates |
| | Prompts | ✅ | Full support |
| | 🔔 Prompts List Changed | ✅ | Real-time updates |
| | Roots | ❌ | Not supported |
| | Sampling | ❌ | Not supported |
| | Completion | ❌ | Not supported |
| Marketplace ||||
| | Server Discovery | ✅ | Browse available servers |
| | Installation | ✅ | Auto configuration |
| Real-time ||||
| | Status Updates | ✅ | Server & connection state |
| | Capability Updates | ✅ | Automatic refresh |
| | Event Streaming to clients | ✅ | SSE-based |
| | Auto Reconnection | ✅ | With backoff |
| Development ||||
| | Hot Reload | ✅ | Auto restart a MCP server on file changes with dev mode |
| Configuration ||||
| | ${} Syntax | ✅ | Environment variables and command execution across all fields |
| | VS Code Compatibility | ✅ | Support for servers key, ${env:}, ${input:}, predefined variables |
| | JSON5 Support | ✅ | Comments and trailing commas in configuration files |
## Simplified Client Configuration
Configure all MCP clients with just one endpoint:
json
"mcpServers" : {
"Hub": {
"url" : "http://localhost:37373/mcp"
The Hub automatically:
Namespaces capabilities to prevent conflicts (e.g., filesystemsearch vs databasesearch)
Routes requests to the appropriate server
Updates capabilities in real-time when servers are added/removed
Handles authentication and connection management
## Key Features
Unified MCP Server Endpoint (/mcp):
Single endpoint for ALL MCP clients to connect to
Access capabilities from all managed servers through one connection
Automatic namespacing prevents conflicts between servers
Real-time capability updates when servers change
Simplified client configuration - just one endpoint instead of many
Dynamic Server Management:
Start, stop, enable/disable servers on demand
Real-time configuration updates with automatic server reconnection
Support for local (STDIO) and remote (streamable-http/SSE) MCP servers
Health monitoring and automatic recovery
OAuth authentication with PKCE flow
Header-based token authentication
Unified REST API:
Execute tools from any connected server