← All resources Product

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 do with the MCP

The MCP answers questions about your data and your tracking, sets up Measurebase with you, and improves your tracking settings. Ask the way you would ask a colleague. These are starting points, not commands.

Ask about your Measurebase data

Ask about your tracking setup

Ask about your Google Tag Manager containers

Ask about your GA4 data

Ask about your Google Ads and Meta Ads data

Answers about GA4, Google Ads and Meta need that account linked to your domain in Measurebase.

Set up Measurebase

Improve your tracking settings

Tag Manager changes land in a workspace named Measurebase, and you preview and publish them yourself. Changes in GA4 and Google Ads go live at once, because those tools have no draft, so they need your confirmation first.

Manage alerts, clients and your team

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

  1. 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.
  2. In the IDE, open Settings → Tools → AI Assistant → Model Context Protocol (MCP), click Add and choose As JSON.
  3. Paste the server, with your token in the header:
{
  "mcpServers": {
    "measurebase": {
      "url": "https://mcp.measurebase.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}
  1. 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, run a tracking audit, propose fixes and apply them into the Measurebase workspace in your Tag Manager container (it never publishes), 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

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

Continue reading

Ready to improve your tracking setup?

Start free, no credit card required. Live in about 15 minutes.

Start free