Skip to main content

​
Claude Code

Add --scope user to use it in every project, or --scope project to commit it to .mcp.json for your team — in a shared file, keep the key in the environment rather than in the file. Check it:
Then ask Claude for something only Routeur knows:
Claude calls find_opportunities, then explain_relation on the pair, and shows you the evidence behind the proof.

​
Claude Desktop

Settings → Developer → Edit Config, then add the server:
Restart Claude Desktop. Routeur’s tools appear in the tools menu, and its three prompts — scan for mispricings, brief me on an event, backtest a price band — appear as commands.
Claude Desktop reads the key from this file, so treat the file as a secret. If your build of Claude Desktop does not offer remote MCP servers, use mcp-remote instead.

​
Getting good answers

  • Point Claude at the concept resources once (routeur://concepts/relations, routeur://concepts/leads-and-fees) at the start of a session about pricing; it stops the usual misreadings.
  • Ask for ids, not names: every tool returns the venue and market id, and explain_relation, market_snapshot and compare_venues take them.
  • Composed tools cost several API requests each. On a free key, ask for one scan at a time rather than a sweep of every category.
/mcp in Claude Code shows which Routeur tools loaded and lets you re-authenticate if you rotate the key.