Connect Gemini CLI

Add the looot MCP server to Gemini CLI, sign in with the browser or a header token, and check it works.

Gemini CLI reaches looot’s catalog, balance and runs over MCP, through a config file and an in-CLI auth command.

Before you start you need a looot account. The runs you make spend the organization’s balance, so top up before your first paid run. See Before your first run.

Sign in with the browser

The server URL is https://api.looot.ai/mcp. Nothing to copy: you sign in on looot.ai, pick the organization to bill and click Connect.

~/.gemini/settings.json

{
  "mcpServers": {
    "looot": {
      "httpUrl": "https://api.looot.ai/mcp"
    }
  }
}

Sign in, inside Gemini CLI

/mcp auth looot

Headless: a token in the header

Only for CI and machines with no browser. Create an agent token in Settings and send it as Authorization: Bearer <token>. Never commit it.

Headless: ~/.gemini/settings.json with a header

{
  "mcpServers": {
    "looot": {
      "httpUrl": "https://api.looot.ai/mcp",
      "headers": {
        "Authorization": "Bearer <agent token from looot.ai Settings>"
      }
    }
  }
}

Check it works

Ask Gemini CLI to call balance or catalog_overview. Both are free. A working connection answers with your available balance, or the catalog’s categories and job counts.

What you see when you connect

The browser opens looot.ai and shows the consent page: which organization to bill, which scopes to grant and how long to stay connected. See The consent page.