Skip to main content

The endpoint

POST https://api.routeur.app/mcp, JSON-RPC over Streamable HTTP. The server is stateless: it sets no Mcp-Session-Id, nothing needs to be kept alive, and GET and DELETE are not used. Responses are plain JSON, so any HTTP client can drive it.
List the tools
Call a tool
A tool result carries the JSON as text content and, for the composed tools, the same object as structuredContent. A failed call comes back as a tool result with isError and a readable message — including rate_limited and daily_quota_exceeded, so the model can wait rather than crash.

SDK clients

Any MCP SDK works; point its streamable-HTTP transport at the endpoint and add the header.
TypeScript
Go

stdio-only clients

Clients that can only launch a local process reach the server through mcp-remote:
mcp-remote runs on your machine and holds the key in its process; the traffic still goes to api.routeur.app over TLS. Prefer a native remote connection where your client supports one.

Discovery

https://api.routeur.app/.well-known/mcp.json and https://routeur.app/.well-known/mcp.json describe the server — endpoint, transport, protocol versions, how to authenticate and what the tools are — without a key. https://routeur.app/llms.txt and /llms-full.txt do the same in plain text for agents that read a site before using it.