compare-run) also runs prompts through the inference gateway and returns latency, tokens, and cost per model.
The server is hosted and read-only over the Stats API. Cursor, Claude Code, Claude Desktop, Continue, and ChatGPT Apps connect directly.
Quota
MCP tool calls are Stats API requests. Each successful data result draws from your organization’s daily quota — the same pool your REST API keys use — and counts toward the organization burst limit. Official MCP connections (OAuth sign-in) are identified server-side asmcp traffic in your usage reports; you do not need to send the X-LLM-Stats-Client header.
Workflow tools such as compare-models chain several API calls and consume one data response per underlying call. See Plans and quotas for limits and counting rules.
Organization-level quota enforcement is planned. Until it ships, MCP calls
are subject to the same route limits as REST calls. See the
changelog.
Setup
Point your MCP client at the hosted server. No installation required.Connect with OAuth (recommended)
On first connect, your MCP client opens a browser sign-in with Google or GitHub. You do not need to copy an API key into client config — the server brokers access behind the scenes.- Cursor
- Claude Code
- Claude Desktop
- Continue
- Other clients
Add this to your Cursor MCP settings (
.cursor/mcp.json):Legacy: API key
If your client does not support OAuth, pass a Stats API key in theAuthorization header. Keys must use the sk_ze_ prefix.
- Cursor
- Claude Code
- Claude Desktop
- Continue
- ChatGPT Apps
- Other clients
Add this to your Cursor MCP settings (
.cursor/mcp.json):Authentication
OAuth (recommended)
When you connect with OAuth, the MCP client discovers the LLM Stats authorization server, opens a browser sign-in, and receives an access token. The MCP server validates that token and provisions a stable per-user API key for Stats and gateway calls — you never paste a key into client config.1
Add the server URL
Configure your MCP client with
https://mcp.llm-stats.com/mcp only (no Authorization header).2
Sign in on first connect
Your client shows Connect or Needs authentication. Complete sign-in with Google or GitHub on llm-stats.com.
3
Use tools
After authorization, tool calls use the brokered credentials automatically. Reconnect later without signing in again until the token expires.
Legacy API key
You can still authenticate with a Bearer token. Use the samesk_ze_... key as the Stats API and the Gateway API. Get yours from the developer console.
Tools
Read tools
Read tools are safe to call at any time. They don’t modify state and don’t consume gateway credits.Workflow tools
Workflow tools chain multiple API calls. They’re still read-only.Gateway tools
Gateway tools call the inference gateway. OAuth-provisioned access and legacysk_ze_... keys both authenticate gateway tool calls.