The MCP gateway that doesn't overwhelm your AI.
MCPHubs
The MCP gateway that doesn't overwhelm your AI.
中文文档 · Quick Start · Connect AI · Configuration
The Problem
MCP is powerful — but naive aggregation is not. When you wire up 10+ MCP Servers, your LLM is force-fed hundreds of tool definitions on every single request — burning tokens, inflating costs, and degrading decision quality.
The Solution: Progressive Disclosure
Instead of dumping every tool into the system prompt, MCPHubs exposes a lean surface of just 3 meta-tools. Your AI discovers servers, inspects their capabilities, and calls the right tool — all on demand, with zero upfront overhead.
┌─────────────────────────────────────────────────────────────────────┐
│ Without MCPHubs │
│ │
│ AI System Prompt: │
│ ├── tool_1 definition (search) } │
│ ├── tool_2 definition (fetch_article) } 150 tool schemas │
│ ├── tool_3 definition (create_issue) } = ~8,000 tokens │
│ ├── ... } EVERY request │
│ └── tool_150 definition (run_analysis) } │
└─────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│ With MCPHubs │
│ │
│ AI System Prompt: │
│ ├── list_servers "discover servers (with search)" } │
│ ├── list_tools "inspect a server's tools" } 3 tools │
│ └── call_tool "invoke any tool" } ≈ 300 tokens│
│ │
│ AI discovers and calls the right tool when needed. Not before. │
└─────────────────────────────────────────────────────────────────────┘
How It Works
MCPHubs collapses all your MCP Servers into 3 meta-tools:
| Meta-Tool | Purpose |
|---|---|
list_servers |
Discover MCP Servers (supports fuzzy search by name/description) |
list_tools |
Inspect tools on a specific server |
call_tool |
Invoke any tool on any server |
The AI explores your tool ecosystem on demand — it calls list_servers to see what's available, drills into a server with list_tools, and invokes the right tool via call_tool. No upfront cost, no bloat.
Scales to hundreds of servers.
list_serversreturns up to 20 results by default, along with the total count. When the AI sees more servers exist than shown, it automatically narrows results with the optionalqueryparameter — no extra tools needed.
Don't need progressive disclosure? Set
MCPHUBS_EXPOSURE_MODE=fulland MCPHubs becomes a straightforward aggregation gateway — all tools from all servers exposed directly.
✨ Features
| 🎯 Progressive Disclosure | 3 meta-tools, infinite capabilities. Tools loaded on demand |
| 🔀 Multi-Protocol Gateway | Unifies stdio, SSE, and Streamable HTTP behind one endpoint |
| 🖥️ Web Dashboard | Modern Next.js UI for managing servers, bulk import/export |
Tools (3)
list_serversDiscover MCP Servers with optional fuzzy search by name or description.list_toolsInspect tools available on a specific MCP server.call_toolInvoke any tool on any connected MCP server.Environment Variables
MCPHUBS_EXPOSURE_MODESet to 'full' to disable progressive disclosure and expose all tools directly.MCPHUBS_CONFIG_PATHPath to the configuration file defining connected MCP servers.Configuration
{"mcpServers": {"mcphubs": {"command": "npx", "args": ["-y", "mcphubs"], "env": {"MCPHUBS_CONFIG_PATH": "/path/to/config.json"}}}}