An MCP gateway with managed server access

AnyRouter runs a Model Context Protocol (MCP) server that turns your workspace into JSON-RPC tools any MCP-capable client can call — Claude Desktop, Claude Code, Cursor, OpenCode, or your own agents. Instead of hand-wiring a script to check your balance or list models, your assistant calls a tool over one stable endpoint:

https://anyrouter.dev/api/v1/mcp

It speaks JSON-RPC 2.0 over the Streamable HTTP transport, so any standard MCP client points at it with no custom code.

The server surfaces your workspace as a small, scoped tool catalog — read your credits, manage keys, inspect presets and conversations, and check system health, straight from your assistant:

The MCP server does not expose a chat tool — clients call the Chat Completions, Messages, or Responses endpoints directly for inference. Administrators see additional admin tools, hidden from everyone else.

Clients authenticate with an OAuth 2.1 bearer token, or a static key: an LLM key (sk-ar-v1-…, which grants list_models only) or a management key (ak_…) carrying the scopes the tools you call require. On the OAuth consent screen the user picks one bundle — Read-only, Standard, or Full — and can downgrade from what a client requests; a tool needing a scope outside the granted bundle returns permission denied.

The dashboard MCP Gateway tab is where you manage this: connect clients, control which tools are exposed and to whom, and watch the same identity and audit trail you already use for inference. Adding a tool doesn't mean re-editing every client's config.

Point your MCP client at the endpoint and authenticate once. Step-by-step client setup for Claude Desktop, Claude Code, Cursor, and OpenCode lives at /docs/api-reference/mcp.