ToolRoute is a remote MCP server that narrows a large tool list to the few tools a task needs, using BM25 keyword ranking.
What you can do
Register a tool list once, in MCP, OpenAI, Anthropic, Gemini or Bedrock form, or point at a public remote MCP server, and get a set_id; the same tools always map to the same set_id, kept 90 days after last use. Ask which tools a task needs by sending a set_id or tool list plus the task query. Get back a ranked shortlist of 3 to 12 tools (or a chosen k), a confidence level, matched terms, token savings and definitions ready to inject in a chosen format.
When to use it
Useful when an assistant has a large tool catalog and you want to inject only the relevant definitions per turn to save context. Suited to keyword-matchable task routing rather than semantic selection.
Requirements
A remote streamable HTTP endpoint; no authentication, environment variables or headers are declared. Free tier is limited to 200 route_tools calls per IP per day; further use is paid via x402 or credits.
Before you install
Routing is BM25 keyword matching, not an LLM, so results depend on wording and confidence may be low or none. The free tier is capped per IP per day and beyond it costs money through x402 or credits. Registering a remote MCP URL lists its tools, which are never called.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/co.youraitools%2Ftoolroute/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Register a tool list once and get a set_id for route_tools. Pass "tools" (array in MCP, OpenAI, Anthropic, Gemini or Bedrock form, max 500) or "url" (public remote MCP server; its tools are listed, never called). Same tools always get the same set_id; sets are kept 90 days after last use. Free.
Parametersurltools
route_tools
Route a task to the right tools (ToolRoute)
Which of my tools does this task need? Send "set_id" (from register_tools) or "tools", plus "query" (the task). Returns a ranked shortlist (adaptive 3-12 tools, or "k"), confidence (high/medium/low/none), matched terms, token savings and the definitions ready to inject ("format": mcp, openai, anthropic, gemini or names). BM25 keyword ranking, no LLM. Free: 200 calls/day per IP, then $0.001 per call via x402 or credits.
Parameterskmax_kqueryrequiredtoolsformatset_id
Version history
2
v0.1.1LatestOct 25, 2026
v0.1.0Oct 24, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.