One MCP. 220+ tools.
Stop wiring up a new API every time your agent needs a capability. One ToolRouter connection ships image, video, scraping, lead, research, SEO, and live-data tools into Claude Code, Cursor, Windsurf, Codex, and Gemini CLI.
MCP + REST. Free tier with no card.
claude mcp add toolrouter
One command. Auto-provisioned account on first use. No key before connecting, no separate signup. Full technical docs at /docs.
Developer FAQ
How do I add ToolRouter to Claude?
The fastest path for Claude Desktop and Web is to paste the ToolRouter MCP URL into Claude Settings → Connectors. For Claude Code or any terminal workflow, run one command: claude mcp add toolrouter -- npx -y toolrouter-mcp.
What is ToolRouter, and how is it different from direct API integrations?
ToolRouter is a hosted gateway that sits between your AI and the tools it needs. Instead of building or managing individual API integrations — one for images, one for leads, one for search — you connect once and get all of them. ToolRouter handles authentication, billing, rate limits, and provider routing automatically.
How do accounts and API keys work?
Connector, MCP, and CLI setups auto-provision an account on first use, so you do not need a key before connecting. If you want dashboard access, credits, billing, or a named API key for REST or manual setup, claim the account after connecting and create keys there.
Does ToolRouter work with Claude Code and other developer tools?
Yes. Claude Code, Cursor, Windsurf, VS Code Copilot, Codex CLI, and Gemini CLI all support ToolRouter via the Model Context Protocol (MCP). Add it once with a single config line and it works across every session and project automatically.
Can I bring my own keys?
Yes. If you already have an account with a provider (fal.ai, ElevenLabs, OpenAI, Perplexity, etc.) you can use your own key and skip the ToolRouter service cost entirely. Your keys are never stored — used once and discarded.
Is there a REST API?
Yes. Every tool is callable over REST at api.toolrouter.com. Create a named API key from the dashboard, send the tool + skill + input, and you get a JSON response. MCP is the fast path for agent setups; REST is there when you need direct control.
How does billing work for programmatic usage?
Flat platform fee of $0.005 per paid call. Free tools stay free. Pay-as-you-go credits cover provider costs (image generation, scraping, etc.) with a transparent per-call breakdown in the dashboard.
Where are the full technical docs?
See /docs for SDK reference, MCP setup across every client, REST endpoints, auth, and the model-selection hierarchy.
Ship your agent with real tools.
MCP + REST. Free tier with no card.