ToolRoute
Orchestrates multi-step tasks across Atlassian services by routing to specialized MCP servers within its catalog.
Handles email operations by identifying and routing tasks to Gmail-integrated MCP servers as part of complex orchestration chains.
Selects and routes tasks to Google's AI models, optimizing for performance and cost across different task tiers.
Automates Jira issue management and updates by routing tasks to the appropriate Jira MCP server.
Integrates Meta's language models into task routing workflows for efficient code and chat generation.
Routes requests to OpenAI models, utilizing intelligent classification to pick the best model for quality and value.
Routes communication tasks to Slack MCP servers to enable automated messaging within agent workflows.
ToolRoute
Routing layer for AI agents. One call returns the best MCP server and LLM for any task — scored on 132 real benchmark executions.
Quick start
Add to any MCP client (Claude Code, Cursor, Windsurf, Cline):
{
"mcpServers": {
"toolroute": {
"url": "https://toolroute.io/api/mcp"
}
}
}Or via HTTP:
curl -X POST https://toolroute.io/api/route \
-H "Content-Type: application/json" \
-d '{"task": "search the web for recent AI papers"}'{
"approach": "mcp_server",
"recommended_skill": "exa-mcp-server",
"recommended_model": "gemini-flash-2.0",
"confidence": 0.91
}Related MCP server: Playwright MCP Server
How it works
Every task falls into one of three approaches:
Approach | When | Returns |
| Task needs only an LLM (code, writing, analysis) | Best model + cost estimate |
| Task needs an external tool (search, email, calendar) | Best tool + best model |
| Compound task ("send Slack AND update Jira AND email") | Ordered orchestration chain |
Routing uses an LLM classifier (~$0.00001/call) for task understanding, then ranks candidates on a 5-dimension score:
Value Score = 0.35 × Output Quality
+ 0.25 × Reliability
+ 0.15 × Efficiency
+ 0.15 × Cost
+ 0.10 × TrustEvery reported outcome updates the scores. The routing gets more accurate as more agents use it.
Benchmark results
132 blind A/B executions across code, writing, analysis, structured output, and translation.
ToolRoute | Fixed GPT-4o | |
Quality wins | 6 | 0 |
Ties | 9 | 9 |
Losses | 0 | — |
Avg cost | $0.001–0.01 | $0.03–0.10 |
API
Endpoint | Method | Description |
| POST | Route a task to best MCP server + LLM |
| POST (JSON-RPC) | MCP server — 16 tools |
| GET (SSE) | SSE transport for MCP clients |
| POST | Report model outcome |
| POST | Verify model output quality |
| GET | Search MCP server catalog |
| POST | Register agent identity |
Full reference at toolroute.io/api-docs
SDK
npm install @toolroute/sdkimport { ToolRoute } from '@toolroute/sdk'
const tr = new ToolRoute()
const rec = await tr.route({ task: 'parse this CSV and summarize it' })
// execute with rec.recommended_model ...
await tr.report({ skill: rec.recommended_skill, outcome: 'success', latency_ms: 1400 })Self-hosting
git clone https://github.com/grossiweb/ToolRoute.git
cd ToolRoute
cp .env.local.example .env.local
npm install
npm run devRequires: NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY
Stack
Next.js 14 (App Router) · Supabase (Postgres) · Vercel
License
MIT
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/grossiweb/ToolRoute'
If you have feedback or need assistance with the MCP directory API, please join our Discord server