
一个为模型上下文协议(MCP)服务器提供动态服务器管理和监控的集中管理
概览
MCP Hub 作为 MCP 服务器和客户端的中央协调器,提供两个关键接口: 1. (/api/*):通过统一的REST API和Web UI管理多台MCP服务器 2.(/mcp):连接任意MCP客户端,通过单一端点访问所有服务器功能 这种双接口方式意味着您可以通过枢纽的界面管理服务器,而MCP客户端(Claude Desktop、Cline等)只需连接到一个端点(localhost:37373/mcp)即可访问所有功能。实现MCP 2025-03-26规范。 配置所有MCP客户端仅有一个端点: 枢纽自动:- 命名空间功能以防止冲突(例如:
概述(AI 翻译)
MCP Hub 作为 MCP 服务器和客户端的中央协调器,提供两个关键接口:
- 管理接口(/api/*):通过统一的REST API和Web界面管理多台MCP服务器
- MCP 服务器接口(/mcp):连接任意 MCP 客户端,通过单一端点访问所有服务器功能
这种双接口方式意味着您可以通过枢纽的界面管理服务器,而MCP客户端(Claude Desktop、Cline等)只需连接到一个端点(localhost:37373/mcp)即可访问所有功能。实现MCP 2025-03-26规范。
功能支持
| 分类 | 特色 | 支持 | 注释 |
|---|---|---|---|
| 交通 | |||
| Streamable-HTTP | ✅ | 远程服务器的主要传输协议 | |
| SSE | ✅ | 远程服务器的备份传输 | |
| STDIO | ✅ | 用于运行本地服务器 | |
| 认证 | |||
| OAuth 2.0 | ✅ | 结合PKCE流 | |
| 头部 | ✅ | 对于 API 密钥/令牌 | |
| 能力 | |||
| 工具 | ✅ | 列表工具 | |
| 🔔 工具列表更改 | ✅ | 实时更新 | |
| 资源 | ✅ | 全力支持 | |
| 🔔 资源列表更改 | ✅ | 实时更新 |
本页由 AI 翻译,技术细节请以原文为准。
README
以下为原文 README 节选,完整内容请查看原文。
MCP Hub
MCP Hub acts as a central coordinator for MCP servers and clients, providing two key interfaces:
- Management Interface (/api/*): Manage multiple MCP servers through a unified REST API and web UI
- 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:
{
"mcpServers" : {
"Hub": {
"url" : "http://localhost:37373/mcp"
}
}
}
The Hub automatically:
- Namespaces capabilities to prevent conflicts (e.g.,
filesystem__searchvsdatabase__search) - Routes requests to the appropriate server
- Updates capabilities in real-time when servers are added/removed
安装
npx -y server-perplexity-ask配置
{
"mcpServers" : {
"Hub": {
"url" : "http://localhost:37373/mcp"
}
}
}