AnyRouter MCP with other clients

Any client that speaks MCP over remote HTTP connects to https://anyrouter.dev/api/v1/mcp with OAuth or a bearer key. The client must support remote HTTP transport (no stdio), and for OAuth, Dynamic Client Registration (RFC 7591) and Authorization Code + PKCE (S256).

OAuth (default)

1. Add a remote MCP server pointing at https://anyrouter.dev/api/v1/mcp.
2. On the first tool call, approve anyrouter.dev/oauth/consent (Read-only is the default).
3. The client stores the token until you revoke it in the MCP dashboard.

Static key (headless, CI)

Send a bearer token instead of OAuth:

• LLM API key (sk-ar-v1-*) from /dashboard/keys: grants list_models, recommend_model, get_system_status, list_okf_concepts, get_okf_concept, plus the artifact tools when the key may use artifacts. Account tools such as get_credits need a management key.
• Management API key (ak_*) from /dashboard/settings#keys: grants the scopes you assign.

curl https://anyrouter.dev/api/v1/mcp \
  -H "Authorization: Bearer ak_your_management_key" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/list","params":{},"id":1}'

A JSON tool list means it works; 401 means the key is wrong. Full reference: MCP API → Manual authentication.

Revoke

Revoke an OAuth token in the MCP dashboard. For static keys, delete the key at /dashboard/keys or /dashboard/settings#keys.