Smithery Toolbox
Install one Smithery Toolbox MCP remote so your agent can be routed to the right registry MCP for the task instead of wiring dozens of servers by hand.
Overview
Smithery Toolbox is a Build-phase MCP server that dynamically routes agent tool calls to other MCPs in the Smithery registry from one hosted endpoint.
What is this MCP server?
- Single entry point that routes agent requests to other MCPs in the Smithery registry
- Streamable HTTP at server.smithery.ai/@smithery/toolbox/mcp
- Bearer Smithery API key required on the remote
- Version 1.0.0 hosted remote—reduces per-integration MCP config sprawl
- Use when task type changes session-to-session and you want registry-backed tool selection
- Server version 1.0.0 per published server metadata
- One streamable-http remote at @smithery/toolbox/mcp
- Designed to route across the full Smithery MCP registry
What problem does it solve?
Maintaining a separate MCP config line for every Smithery server burns time and breaks when you only need one integration for today’s task.
Who is it for?
Power users who want a single Smithery hub while experimenting with many registry MCPs during agent-assisted development.
Skip if: Production environments that require a minimal fixed MCP allowlist with no dynamic third-party routing.
What do I get? / Deliverables
One Toolbox remote registration lets the agent reach registry MCPs on demand instead of you curating a long static server list.
- Unified Smithery MCP entry point in agent config
- On-demand routing to registry MCPs during sessions
- Lower manual MCP server list maintenance
Recommended MCP Servers
Journey fit
Toolbox is meta infrastructure for how agents call tools during product work, which belongs on the Build shelf under agent tooling before phase-specific integrations. Dynamic routing across the Smithery MCP registry is explicitly about expanding agent capability surface—not shipping app frontend or running production monitors.
How it compares
Registry router MCP—not a domain skill and not a substitute for a dedicated single-purpose integration when you need predictable behavior.
Common Questions / FAQ
Who is Smithery Toolbox for?
Indie builders and agent-heavy developers who pull many Smithery MCPs over time and want one routing remote instead of endless client entries.
When should I use Smithery Toolbox?
Use it at the start of build and agent-tooling setup when your workflow spans multiple external systems and you prefer Smithery to pick the matching registry MCP.
How do I add Smithery Toolbox to my agent?
Add https://server.smithery.ai/@smithery/toolbox/mcp as a streamable-http MCP remote with Authorization Bearer {smithery_api_key}.