# Claude Code

One command. OAuth by default; a header for CI and containers.

Sign in with browserAPI key

## Setup

1.  1
    
    Add the server. Run /mcp inside a session to complete the login.
    
    **Terminal**
    
    ```
    claude mcp add --transport http zomler https://api.zomler.com/mcp
    ```
    
2.  2
    
    For CI, a container or a shared machine, pass a key and there is no login step.
    
    **Terminal, with a key**
    
    ```
    claude mcp add --transport http zomler https://api.zomler.com/mcp \
      --header "Authorization: Bearer zk_live_…"
    ```
    
3.  3
    
    Scope it to a project with --scope project to check the config into .mcp.json for the team. Keep keys out of that file; use the OAuth form there.
    

## What you get

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

Keys are created under [API keys](https://app.zomler.com/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](https://zomler.com/docs/api).

[All clients](https://zomler.com/docs/mcp)

---

Source: https://zomler.com/docs/mcp/claude-code