Mcp Broker
Collapse dozens of upstream MCP servers behind one local broker entry so your agent config stays small and you run mcp-broker init before wiring clients.
Overview
mcp-broker is a MCP server for the Build phase that locally brokers many upstream MCP servers behind one compact stdio entry for agent clients.
What is this MCP server?
- Local MCP broker exposing one compact client entry for many upstream servers
- PyPI mcp-broker 1.3.1 with stdio transport; install via pipx install mcp-broker
- Publisher note: run mcp-broker init before rendering a local client entry
- Reduces MCP config sprawl for Claude Code and desktop MCP hosts
- Open source at NavinAgrawal/mcp-broker (websiteUrl points to README)
- Package version: mcp-broker 1.3.1 (PyPI, stdio)
- Recommended install: pipx install mcp-broker
- Required setup step: mcp-broker init (publisher-provided note)
Community signal: 1 GitHub stars.
What problem does it solve?
Every new MCP server bloates your client config and makes it painful to swap or gate tools across many integrations.
Who is it for?
Power users running five or more MCP servers locally who want one maintainable entry in Claude Code or similar hosts.
Skip if: Beginners with a single MCP server who do not need indirection or local routing complexity.
What do I get? / Deliverables
You register one broker-backed MCP entry and route agent tool calls to the upstream servers you configured after mcp-broker init.
- Single compact MCP client entry proxying many servers
- Centralized local routing for upstream MCP tools
- Init-generated broker config ready for your agent host
Recommended MCP Servers
Journey fit
MCP aggregation is build-phase integration work: you are composing the agent tool surface before you ship or scale how many servers you maintain. Integrations subphase fits a broker that fronts many upstream MCP servers through one compact stdio entry—not a single-vendor API skill.
How it compares
Local MCP multiplexer and config compressor, not a curated remote marketplace or a domain-specific API server.
Common Questions / FAQ
Who is Mcp Broker for?
Indie builders and developers who run multiple MCP servers locally and want one broker entry instead of duplicating client configuration.
When should I use Mcp Broker?
Use it during build when your agent tooling stack grows past a few stdio servers and you need centralized routing and a compact client manifest.
How do I add Mcp Broker to my agent?
Run pipx install Mcp Broker, execute Mcp Broker init per the README, then point your MCP client at the generated local broker stdio entry.