Connect JetBrains AI Assistant to Measurebase
Measurebase speaks MCP - the open protocol AI assistants use to reach external tools - and JetBrains AI Assistant speaks it too, in every JetBrains IDE. Add Measurebase as a remote server and your tracking answers show up in the AI chat next to your code.
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."
AI Assistant 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
- In the Measurebase dashboard, create a personal API token under Settings → API tokens. It is read-only by default and valid until you revoke it.
- In the IDE, open Settings → Tools → AI Assistant → Model Context Protocol (MCP), click Add and choose As JSON.
- Paste the server, with your token in the header:
{
"mcpServers": {
"measurebase": {
"url": "https://mcp.measurebase.com/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}- Apply. The server shows a green status with its tools; open the AI Assistant chat and ask away.
🔑 Why a token here?
AI Assistant connects to remote MCP servers with the headers you give it and has no browser-based OAuth flow of its own, so the token stands in for the consent screen - with the same scope choice (read-only unless you create a read & write token) and the same one-click revocation under Settings → API tokens.
🔒 Read-only by design
New connections are read-only unless you explicitly tick read & write on the consent screen - and read-only means exactly that: it can never change anything, not your domains, not your settings, not your tokens. With write access the assistant can also toggle power-ups, verify DNS, generate tracking scripts, and set up new accounts and domains (returning the exact DNS record to add) - never more than your own role on each account allows, and Auto Grant Consent is excluded permanently.
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.
🤝 For agencies
Your connection follows your agency access too: clients who approved your link are queryable in the same conversation. "Which of my clients had alerts this week?" is one question instead of ten dashboard visits.