Connect Gemini CLI to Measurebase

Measurebase speaks MCP - the open protocol AI assistants use to reach external tools - and Google's Gemini CLI speaks it too. Register Measurebase once and your tracking answers arrive in the terminal, in the middle of whatever you were doing.

What you can ask

• "How much traffic did we process this month, and which domain was busiest?"
• "Are there any open alerts on my accounts?"
• "Is Enhanced Ad Blocker Protection actually working on my site?"
• "Did my test hit from five minutes ago arrive?"
• "How far into my request quota am I this billing cycle?"
• "Compare last week's consent-denied share to the week before."
• "Generate the tracking script for my new domain."

Gemini answers with your live data: statistics, request types, browser and bot breakdowns, Consent Mode v2 signals, request logs, alerts, plan usage, and the ad-block detection status - across every account you're a member of.

Connect in two minutes

1. In a terminal, run gemini mcp add --transport http measurebase https://mcp.measurebase.com/mcp - or add the server to ~/.gemini/settings.json by hand (.gemini/settings.json inside a project keeps it project-scoped):

{
  "mcpServers": {
    "measurebase": {
      "httpUrl": "https://mcp.measurebase.com/mcp",
      "oauth": { "enabled": true }
    }
  }
}

2. Start gemini and run /mcp auth measurebase. Gemini CLI opens your browser for the Measurebase login and shows the consent screen that spells out what it gets.
3. Click Allow. /mcp lists the Measurebase tools; ask your question at the prompt.

The OAuth flow needs a local browser and a localhost redirect. On a headless machine or inside a container, use a token instead.

Prefer a token?

You can skip the OAuth flow with a static header. Create a personal API token in the dashboard under Settings → API tokens (read-only by default, valid until you revoke it) and add it to the server entry instead of the oauth block:

"headers": { "Authorization": "Bearer YOUR_TOKEN" }

Keep it in your user settings, not in a project file that ends up in version control.

How access and privacy work

• Personal, not account-wide. A connection authenticates as you and follows your own memberships: it sees the accounts you can see, nothing else. Colleagues connect for themselves.
• Your roles apply, live. Every request re-checks your membership and role on the account it touches. Lose access to an account and the connection loses it that same second.
• Revocable in one click. Every connection shows up under Settings → API tokens - OAuth ones included. Revoke it there and the connection is dead immediately.
• Nothing is stored in between. The connector service keeps no credentials and no data; it forwards your token to the Measurebase API over TLS and returns the answer. Only a hash of any token is ever stored server-side.
• Standards, not improvisation. The flow is OAuth 2.1 with mandatory PKCE and single-use, short-lived authorization codes.