← Guides·Analytics MCP servers

Analytics MCP servers

Google Tag Manager MCP: is there an official server?

Google ships no Tag Manager MCP server. What third-party GTM servers can do through the API, which scopes let them publish, and what to check first.

David PombarSwiss army knife at Trackingplan
6 min read · 1273 words

TL;DR Google doesn’t publish a Google Tag Manager MCP server. Third-party servers wrap the Tag Manager API v2, which covers reading, editing, versioning and publishing containers. The scope a server asks for decides how far it can go. Read-only needs one scope; the widest servers ask for all seven.

Analytics MCP servers mostly read reports. A Tag Manager server is different: it can change what runs on your site. This page covers what exists, what the API allows, and what to check before you connect one. It’s part of our map of analytics MCP servers.

The seven Tag Manager API scopes from read-only to account management, with the effect of each one, from viewing containers to publishing a version to the live site.
Each scope widens what the server can do, up to publishing a version to the live site.

Is there an MCP server for Google Tag Manager?

Not from Google. As of 16 November 2026, Tag Manager isn’t in Google’s own list of the remote and open-source MCP servers it publishes, and it isn’t in Google Cloud’s product list of managed remote ones.

What exists are third-party servers built on the Tag Manager API v2. Search for one and you get a long list on MCP directories: open-source repositories by individual developers, agency projects and hosted services. They aren’t Google’s, however the listing reads.

Google does publish an MCP server for the reporting side, the Google Analytics MCP server. It doesn’t read or write GTM.

What a GTM MCP server can do: the scopes

Every GTM server is a wrapper around the Tag Manager API, and the API is gated by OAuth scopes. The scope list is the most honest description of what a server can do. From Google’s authorisation guide:

ScopeGoogle’s descriptionWhat it means in practice
tagmanager.readonlyView your Google Tag Manager containersRead tags, triggers, variables and versions
tagmanager.edit.containersManage your Google Tag Manager containersCreate and change tags, triggers and variables in a workspace
tagmanager.delete.containersDelete your Google Tag Manager containersRemove containers
tagmanager.edit.containerversionsManage your Google Tag Manager container versionsCreate and change versions
tagmanager.publishPublish your Google Tag Manager containersPush a version live
tagmanager.manage.usersManage user permissions of your Google Tag Manager dataGrant and remove access
tagmanager.manage.accountsManage your Google Tag Manager accountsChange account settings

The token also acts as you: the server reaches the accounts and containers your Google account can reach. If you’re an admin, so is the assistant.

The most widely listed GTM server is published by Stape, in the GitHub repository stape-io/google-tag-manager-mcp-server, under the Apache 2.0 licence. It isn’t from Google, and we don’t vouch for it. Its README is clear about what it is, which makes it a useful example. As of 16 November 2026, per its README and source:

A server meant to build containers needs those scopes. Connecting it still hands the assistant everything your GTM account can do.

Why write access to GTM is a different risk

Change a GA4 custom dimension by mistake and a report looks odd. Publish a GTM version by mistake and every page that loads the container runs it: a purchase tag that fires twice, a consent check removed, a pixel sent before the visitor answers the banner.

GTM already has the safety net. Changes happen in a workspace and only reach the site when someone publishes a version. Keep that line:

Check a GTM server before you connect it

  1. Who publishes it? A company with a support channel or an individual repository. Either can be fine; know which.
  2. Which scopes does it request? Look in the source, not only the README. Read-only work needs tagmanager.readonly alone.
  3. Where does the token live? Locally, or on the publisher’s servers.
  4. Which tools write? Then set each one to need approval in Claude, or keep ChatGPT on asking first.
  5. Which account do you connect with? A user with Read access on one container is safer than an admin on all of them.

For the wider audit of a container, before or after an AI touches it, see our GTM audit checklist.

What the Tag Manager API can’t tell you

The API returns configuration: what the container says should happen. It doesn’t return what happened. A tag can be set up correctly and still fail in production: the dataLayer push arrives after the trigger, a variable reads an empty path on one template, the consent state blocks it in one market. An MCP server hands the model whatever the platform stores, and for GTM that’s the plan, not the result. Debugging that gap is its own job; our dataLayer debugging guide covers it.

Trackingplan works from the other side. It finds your GTM containers in your own traffic and captures every published release, with no setup, so it can line up a release with a broken event or a drop in traffic. It watches the hits each tag sends, with the dataLayer and the consent state, on real traffic. When the fix is in GTM, it explains the problem, prepares the change in a separate workspace, tests it on the site with and without the change, and leaves publishing to you.

Trackingplan MCP brings that into Claude, ChatGPT or Cursor. Each person signs in as themselves, with no API key, and any change to the plan waits for approval. Ask it what changed in a container and when, or which release lines up with a broken event. The setup is in the MCP endpoint docs.

FAQ

Is there an MCP server for Google Tag Manager?

Not one from Google. As of 16 November 2026, Tag Manager isn’t in Google’s MCP repository or in Google Cloud’s list of managed remote MCP servers. Third-party servers built on the Tag Manager API v2 exist, Stape’s among them, and they can read and change containers.

Can a GTM MCP server publish changes to my live site?

Yes, if it asks for the tagmanager.publish scope and your account can publish. A published container version goes live on every page that loads the container, so keep publish and delete tools on approval or blocked.

Which scope does a read-only GTM MCP server need?

tagmanager.readonly, which Google describes as view your Google Tag Manager containers. Edit, delete, publish, user and account management each have their own scope.

Can an AI assistant tell if my GTM tags actually fire?

Not through the Tag Manager API. The API returns the container’s configuration: tags, triggers, variables and versions. Whether a tag fired, with which parameters and under which consent state, is only visible in the requests the site sends.

David PombarSwiss army knife at Trackingplan

Read more from David, a Senior Product Strategist with 18+ years in digital product development and an atypical error detection knack.

Trackingplan

See everything. Miss nothing.

Your implementations audited around the clock with real-time, real-user data. Real-time alerts about errors or changes in your data, campaigns, pixels, privacy and consent. Let AI flag issues before they cost you.