← All resources Product

Connect n8n to Measurebase

Measurebase speaks MCP - the open protocol AI assistants use to reach external tools - and n8n's AI Agent can call MCP servers as tools. That turns your tracking data into something a workflow can act on: a Monday-morning digest per client, an alert forwarded to the right channel, a weekly consent check.

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

The agent 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. Read-only is the default and enough for reporting; a workflow that should toggle power-ups needs a read & write token.
  2. In n8n, add an AI Agent node and attach an MCP Client Tool node under its Tools.
  3. Configure the tool: Endpoint https://mcp.measurebase.com/mcp, Server Transport HTTP Streamable, Authentication Bearer, and a credential holding the token.
  4. Give the agent its task in the prompt - "Summarise this week's traffic, open alerts and consent rate for every account I can see" - and connect a Slack, email or Google Sheets node to deliver the answer. A Schedule Trigger makes it recurring.

🔑 Tokens, not OAuth

A workflow runs unattended, so it authenticates with a token you created for it (n8n's MCP Client Tool also accepts OAuth2 credentials, but the consent screen expects a person in front of a browser). Create a separate token per workflow and revoke it under Settings → API tokens when the workflow retires.

Workflows worth building

🔒 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