McpHub
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
McpHub
MCP bridge -- folds the capabilities (tools / prompts / resources) of multiple MCP servers into 4 fixed tools, exposed uniformly to AI tools.
Quick Start
stdio mode (default)
dotnet run --project src/McpHub -- --config examples/mcp-hub.config.jsonConfigure in your AI tool's mcp.json:
{
"servers": {
"mcp-hub": {
"command": "dotnet",
"args": [
"run",
"--project", "path/to/McpHub",
"--", "--config", "path/to/mcp-hub.config.json"
]
}
}
}HTTP mode
dotnet run --project src/McpHub -- --http --port 8080 --config examples/mcp-hub.config.jsonClient connects to http://localhost:8080/ (Streamable HTTP).
Related MCP server: Relay
CLI Options
Option | Alias | Description | Default |
|
| Path to the MCP configuration file | Auto-discovered |
| - | Use HTTP (Streamable HTTP) transport | stdio |
| - | HTTP mode listening port | 8080 |
|
| Workspace folder for | Current directory |
| - | Output verbose diagnostic logs to stderr | Off |
暴露的 3 个 Tool
Tool | 说明 |
| 列出所有上游 MCP server 的可用能力(tools/prompts/resources),可选 |
| 查询某个能力的完整调用方式(参数 schema 等),输入限定名 |
| 实际调用某个能力,传入限定名 + arguments |
配置文件格式
兼容 VS Code 族(servers 键)和 Claude/Cursor 族(mcpServers 键),自动推断 transport 类型:
{
"servers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/path"],
"env": { "API_KEY": "..." }
},
"remote-server": {
"type": "http",
"url": "https://example.com/mcp",
"headers": { "Authorization": "Bearer xxx" }
}
}
}支持变量替换:
${workspaceFolder}— 工作区目录${env:VAR_NAME}— 环境变量
配置文件发现顺序(未指定 --config 时):
--config显式指定当前目录
mcp.json当前目录
.mcp.json.vscode/mcp.jsonclaude_desktop_config.json
架构
AI 工具 ←stdio/http→ McpHub ←stdio/http→ 多个上游 MCP Server
│
├── list_mcp_capabilities → 聚合所有 server 的 tools/prompts/resources
├── describe_mcp_capability → 透传 schema 详情
└── call_mcp_capability → 透传调用详见 设计文档。
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
The OpenRouter for tools. One MCP connection gives any AI agent 254 hosted tools, pay per call.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables LLMs to inspect and test other MCP servers by listing and calling their tools, reading resources, and getting prompts. Supports stdio, SSE, and HTTP transports for both local and remote MCP server inspection.76 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.7 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to manage, aggregate, and proxy other MCP servers dynamically, so they can search, add, configure, enable, disable, and use tools from multiple servers at runtime.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible applications to manage and use local or cloud-hosted models, including listing, pulling, generating, chatting, embeddings, and web search/fetch through a unified tool interface.897 npmAGPL 3.0