MCP

Your coding assistant, briefed on every model

Final Router runs a public Model Context Protocol server. Connect it once and the AI tool writing your integration can look up live models, capabilities, prices and provider health - instead of hardcoding a guess that drifts.

Connect once and the assistant writing your integration queries live models, prices and provider health - instead of hardcoding a guess that drifts.

What it knows

Four tools need no key and reveal nothing about your account: list_models (the catalogue with capabilities, prices and the <provider>/best aliases), get_model, estimate_cost (band-aware list price) and provider_status (live probe health, the same numbers as /status).

What this looks like in practice

You: "Which Final Router model is cheapest with vision and tools,
      and what would 50k input / 5k output tokens cost on it?"

Your assistant calls:
  list_models      -> filters by capabilities.vision && capabilities.tools
  estimate_cost    -> exact USD at list price, peak/long-prompt bands included
  provider_status  -> confirms the provider is healthy right now

...and writes your integration against the answer instead of a guess.

And three that know your account

Send a management key as an Authorization: Bearer header and three more appear: account_spend (balance, spend against the previous window, budget used), api_key_status (every key against its caps - rolling 24h against the daily limit, month to date against the monthly one) and spend_by_model (where the money went). So “what have I spent this month” and “which key is near its cap” are answerable from the editor rather than the dashboard.

A management key, not a gateway key, and the difference is the point: a management key administers and cannot spend a cent. An MCP config is a file that syncs between machines and gets pasted into issues, so the credential in it should be one that reads figures rather than one that can burn a budget. Gateway keys are refused here.

Connect your tool

Pick yours - the URL is the same everywhere, only the file it lives in differs. No token field anywhere: the server is public by design.

MCP server URL

https://finalrouter.com/api/mcp

1Open Settings → Connectors → Add custom connector
2Paste https://finalrouter.com/api/mcp as the URL and save
3On builds without connectors, use the mcp-remote bridge config below instead

claude_desktop_config.json (bridge fallback)

{
  "mcpServers": {
    "finalrouter": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://finalrouter.com/api/mcp"]
    }
  }
}

And the other direction: run your tool ON Final Router

Connecting the MCP server briefs your assistant; pointing your tool’s model provider at Final Router routes the assistant’s own inference through the gateway - fallback, spend caps and usage tracking included. The integrations page has those configs.