[ docs ]MCP · Editor

Cursor

Cursor runs OAuth itself, or takes a key from mcp.json.

Setup

1
Use the install button, or add the server by hand to ~/.cursor/mcp.json (global) or .cursor/mcp.json (one project).
mcp.json
```
{
  "mcpServers": {
    "zomler": {
      "url": "https://api.zomler.com/mcp"
    }
  }
}
```
Cursor shows a Needs login badge. Click it and approve in the browser.

Headless or on a machine with no browser? Send a key instead and skip the login.

mcp.json with a key

{
  "mcpServers": {
    "zomler": {
      "url": "https://api.zomler.com/mcp",
      "headers": { "Authorization": "Bearer zk_live_…" }
    }
  }
}

What you get

One tool per platform, plus capabilities and check_balance, at https://api.zomler.com/mcp. Every answer is the envelope: what was measured, when, what was left out and why, and what it cost. Fresh fetches spend credits; anything already held is free.

Keys are created under API keys in the dashboard, where each one's calls and spend are listed. Revoking a key stops this client on its next call. The same key also calls the REST API.

All clients