Get started

ToolRouter Docs

ToolRouter is a hosted MCP gateway. One catalog of tools for Claude, ChatGPT, and Grok. Companies use ToolRouter to centralize MCP — one connection, one catalog, seats when teams share, and an audit log. Agents and humans connect once, discover the catalog, call skills through a single interface, and get the same response shape back every time.

Why do these ToolRouter docs exist?

These docs exist so both humans and AI agents can access the same onboarding content. Humans browse on the website, agents read the same markdown via the CLI with toolrouter docs. The source lives in docs/content/*.md, keeping product documentation close to the code that powers the platform.

  • Humans can browse the docs on the website.
  • Agents can read the exact same markdown in the CLI with toolrouter docs.
  • The source of truth lives in docs/content/*.md, so product docs stay close to the code.

Start with ToolRouter

Start here

  • AI info for official ToolRouter facts written for ChatGPT, Claude, Gemini, Perplexity, Copilot, and Grok.
  • Quickstart for the shortest path to a successful call.
  • Overview for the product model: tools, skills, keys, and usage.
  • Add to Your Product for giving your existing AI agent access to the full tool catalog through one integration.
  • Integration for MCP, REST, auth, rate limits, and asset delivery.
  • Claude Cowork for adding ToolRouter to Claude Desktop's agentic Cowork mode.
  • PII Filter for the team-level toggle that blocks customer PII from leaving tool calls and redacts it from responses.
  • API Reference for the complete REST endpoint documentation.
  • Files and Media for uploading local files, passing ToolRouter file IDs, and handling generated assets.
  • Billing for credits, pricing, BYOK rates, and the Stripe-backed billing flow.
  • CLI for local development, config, and day-to-day commands.
  • Building Tools for building new first-party tools or plugins.
  • Architecture for the runtime flow across registry, gateway, billing, assets, and knowledge.
  1. Read Quickstart.
  2. Run npx -y toolrouter-mcp docs quickstart in the terminal so the same guide is available in-agent.
  3. Inspect the live catalog with npx -y toolrouter-mcp tools or GET /v1/tools.
  4. Call one tool from the CLI: npx -y toolrouter-mcp call web-search search --query "test".
  5. If you are building on the platform, continue with Building Tools and Architecture.

Connect ToolRouter

Add ToolRouter once, then use the same catalog in the assistants your team already runs.

Compare ToolRouter

Head-to-head guides for companies choosing a hosted catalog versus app connectors, workflow canvases, model routers, or enterprise MCP control planes.

ToolRouter resources

What does ToolRouter include?

The catalog includes tools spanning SEO analysis, App Store ASO, DNS and domain intelligence, website crawling, web scraping, web search, audio generation, image generation, security scanning, and more. Every tool follows the same contract:

  • one tool manifest with JSON Schema inputs
  • one or more callable skills
  • one billing model (credit-based, usage-metered via Stripe)
  • one discovery surface across CLI, MCP, REST, and the website