One endpoint. All your MCP servers.
- Context cost — Every MCP server loads all tool schemas upfront. With dozens of servers, that's a lot of tokens before you even start.
- Config everywhere — Every project needs its own
.mcp.json. Change a server, update every project. - Different needs — Web projects need Chrome DevTools. Backend needs database tools. iOS needs Xcode tools.
MCP Router solves this with one HTTP endpoint that routes to all your servers, progressive tool discovery, and workspace-based configuration.
- Single Endpoint — Configure servers once, connect from anywhere via
localhost:19104 - Progressive Disclosure — AI queries tool schemas on demand, not all at once
- Workspaces — Different projects use different server combinations via tokens
- One-Click Setup — Auto-configure Claude Code and Codex from the app
Download from GitHub Releases, unzip, and move to Applications.
Open the app → Settings → Servers. Add your MCP servers (stdio or http).
One-click from app (Settings → Integration), or manually:
claude mcp add mcp-router -- npx -y mcp-remote http://localhost:19104Restart Claude Code. It now sees 4 meta tools:
| Tool | Purpose |
|---|---|
mcp_router__list_servers |
List available servers |
mcp_router__list_tools |
List tools for a server |
mcp_router__describe |
Get tool parameter schema |
mcp_router__call |
Call a backend tool |
AI uses these to progressively discover and call your actual tools.
Different projects can use different server combinations:
- Create a workspace in Settings → Workspaces
- Select which servers to enable
- Get a token
- Add the token to your project's
.mcp.json:
{
"mcpServers": {
"mcp-router": {
"type": "http",
"url": "http://localhost:19104",
"headers": {
"X-Workspace-Token": "your-token"
}
}
}
}Without a token, requests use the Default Workspace.
git clone https://github.com/vimo-ai/mcp-router.git
cd mcp-router && ./scripts/build-core.sh
open mcp-router.xcodeproj # Cmd+R- Why MCP Router? — The problems and our approach
- Installation — Download and configure
- Usage Guide — Workspaces, tokens, troubleshooting
- Architecture — Technical details