Name: ToolRoute
Author: grossiweb

LABSCO SUMMARY

A second opinion on tool and model choice, cheap enough to ask every turn.

Hardcoding one model and one scraper at build time is the thing that quietly costs money as the task mix changes. ToolRoute answers per task and takes your reported outcomes back, so the answer drifts toward what works on your own workload rather than a public benchmark.

What it is

A hosted routing layer for agents. You describe a task, it names the MCP server and the model to use and returns a confidence score; you still make the call yourself.

What you get

A recommended MCP server plus a recommended model for one task, with alternatives and a fallback
Model-only routing when the task needs no external tool
An ordered chain for compound tasks that touch several tools
Outcome reporting, so later recommendations reflect what actually worked on your traffic
A catalog search over the MCP servers it knows about
A health endpoint and public aggregate metrics

Requirements

Nothing to install for the MCP path — point a client at the hosted endpoint. The SDK is published as @toolroute/sdk; the registry entry io.github.grossiweb/toolroute installs @toolroute/sdk over stdio. Self-hosting needs Supabase credentials.

Setup effort

One command — npx -y @toolroute/sdk@0.2.2 toolroute-mcp

See installation options

USE CASES

01

Picking a model per message, not per project

Route each incoming message, then call your existing provider SDK with the slug it returns. Short varied tasks benefit most.

02

Choosing a tool for an unplanned step

Describe the step in words and get a server name back, with alternatives and a fallback if the first choice is unavailable.

03

Knowing when no tool is needed

Tasks that only need an LLM come back as model-only, which stops an agent from reaching for a scraper to answer a question about scraping.

04

Building a record of what worked

Report success, latency and token counts after each call; later routing responses reflect that history for similar task shapes.

3 tools

Listed in project docs. Your client may show a different list.

toolroute_register

toolroute_route

toolroute_report

BEFORE YOU INSTALL

What to know first

Tools you get

The project says 16; its docs name 3.

Requires

A client that can reach a remote MCP server over HTTP

Where it runs

All 4 documented clients connect to a hosted endpoint.

INSTALLATION

Connect your client

Server setup

npx

TERMINAL

npx -y @toolroute/sdk@0.2.2 toolroute-mcp

Hosted endpoint

ENDPOINT URL

https://toolroute.io/api/mcp

Add this hosted endpoint to your MCP client.

MCP Clients

Claude Code

CLAUDE CODE · JSON

{
  "mcpServers": {
    "toolroute": {
      "type": "http",
      "url": "https://toolroute.io/api/mcp"
    }
  }
}

Cursor

CURSOR · JSON

{
  "mcpServers": {
    "toolroute": {
      "url": "https://toolroute.io/api/mcp"
    }
  }
}

Windsurf

WINDSURF · JSON

{
  "mcpServers": {
    "toolroute": {
      "serverUrl": "https://toolroute.io/api/mcp"
    }
  }
}

Cline

CLINE · JSON

{
  "mcpServers": {
    "toolroute": {
      "type": "streamableHttp",
      "url": "https://toolroute.io/api/mcp"
    }
  }
}

ToolRoute