# Gemini CLI

Remote HTTP servers go in settings.json with a headers block.

API key

## Setup

1.  1
    
    Add the server to ~/.gemini/settings.json (or the project's .gemini/settings.json).
    
    **settings.json**
    
    ```
    {
      "mcpServers": {
        "zomler": {
          "httpUrl": "https://api.zomler.com/mcp",
          "headers": { "Authorization": "Bearer zk_live_…" }
        }
      }
    }
    ```
    
2.  2
    
    Run /mcp inside gemini to confirm the tools are listed.
    

## 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/gemini-cli
