Connect Cursor to Measurebase

Measurebase speaks MCP - the open protocol AI assistants use to reach external tools - and your editor speaks it too. Add Measurebase to Cursor as a remote MCP server and your tracking answers arrive without leaving the file you're working in.

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."

Cursor 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. Open Cursor Settings → Tools & MCP and choose New MCP Server - this drops you into ~/.cursor/mcp.json (use .cursor/mcp.json inside a project for project-scoped config).
2. Add the server:

{
  "mcpServers": {
    "measurebase": {
      "url": "https://mcp.measurebase.com/mcp"
    }
  }
}

3. Cursor discovers the Measurebase authorization server on its own (the MCP authorization spec), opens your browser for the Measurebase login, and shows the consent screen that spells out what it gets.
4. Click Allow. The Measurebase tools appear under the server - ask away in the chat.

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:

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

One caution: a project's .cursor/mcp.json tends to end up in version control - keep token headers in your global config, or stick with OAuth.

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.