Skip to main content
Claude Code adds the Routeur MCP server with a single claude mcp add command and reads the key from your shell. Claude Desktop and claude.ai reach the same server as a custom connector, with the key stored as a request header. Both use https://api.routeur.app/mcp and the same API key as REST.

Claude Code

Export the key, then add the server. --transport http is the Streamable HTTP transport; --header is sent on every request.
The project form, with the key expanded from the environment at load time:
.mcp.json
Claude Code expands ${VAR} and ${VAR:-default} in .mcp.json. Syntax and scopes are from code.claude.com/docs/en/mcp, checked on 2026-09-17.

Verify

Inside a session, /mcp lists the connected servers, their tools and lets you reconnect after rotating a key. Then ask for something only Routeur knows:
Claude should call search_markets (query detroit buffalo total points, cross_venue: true), then compare_venues with the event it found. The observed result on 2026-09-17, trimmed:
A correct answer names Kalshi as 1¢ cheaper for the Over (52¢ against 53¢), gives the observed_at of each price, and does not call a 1¢ gap money without checking find_opportunities.

Claude Desktop and claude.ai

Remote servers are added as custom connectors, not in claude_desktop_config.json (that file only launches local stdio servers; see the alternative below). Custom connectors are available on Free, Pro, Max, Team and Enterprise plans, and the connection is made from Anthropic’s cloud, which reaches api.routeur.app without any change on your side.
  1. Open Customize > Connectors (Team and Enterprise owners: Organization settings > Connectors, then Add > Custom, type Web).
  2. Click Add custom connector. Name it Routeur; MCP server URL https://api.routeur.app/mcp.
  3. Under Authentication choose No sign-in: Routeur authenticates with an API key, not OAuth.
  4. Open Request headers, pick authorization from the list, and enter the value exactly as Bearer rk_live_..., including the word Bearer and the space. Claude sends the value verbatim and stores it without showing it again. Mark the header Required.
  5. Click Add, then enable Routeur for a conversation from the + menu under Connectors.
Routeur’s prompts (scan_for_mispricings, brief_me_on_event, backtest_price_band) and resources appear in the same + menu. Steps and field names are from claude.com/docs/connectors/custom/remote-mcp, checked on 2026-09-17.
Request-header authentication is marked as beta by Anthropic and rolling out by organisation. If the Request headers section is missing from your dialog, use the mcp-remote configuration below, which runs on your machine and adds the header itself.

If your client only launches local servers

claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows: %APPDATA%\Claude\claude_desktop_config.json) can launch mcp-remote, which bridges stdio to the remote server. The header is passed through an environment variable because some clients mangle spaces inside args:
claude_desktop_config.json
Restart Claude Desktop after saving. The file then holds the key, so treat it as a secret.

Getting good answers

  • Start a pricing session by having Claude read routeur://concepts/prices and routeur://concepts/relations; they cost nothing and stop the usual misreadings (spread as edge, “not proven” as “unrelated”).
  • Ask for ids: every tool returns venue and id, and explain_relation, market_snapshot, get_market_book and get_market_rules take them. Titles are not ids.
  • Composed tools cost several requests (market_snapshot five, find_opportunities up to four). On a free key (30 per minute, 2,000 per day) ask for one scan at a time.
  • Put the ten facts in CLAUDE.md or the project’s instructions if the project is about market data; the server’s own instructions cover only the three most important.