Whathead
  • Builder
  • MCP server
  • Transfer
  • Guardrails
  • Pricing
  • Blog
  • Docs
Log inSign up free
  1. Home
  2. MCP server
  3. Google Tag Manager MCP (GTM MCP)
Google Tag Manager MCP (GTM MCP)

Google Tag Manager MCP server for Claude, ChatGPT and Cursor

Whathead's Google Tag Manager MCP server connects Claude, ChatGPT and Cursor to the Tag Manager API v2. The assistant can audit a container and create or edit tags, triggers, variables, templates and folders in a workspace, then create a version and publish it. Whathead has no dry run for GTM: your safety step is the workspace, which stays off the site until a version is published.

Updated 18 Nov 2026
Start a 14-day trialSee pricing
GTM API actions
106 (39 read-only)
Audit
Read-only container and workspace audit
Before publish
Edits stay in a GTM workspace
Read-only connector
https://www.whathead.com/mcp/read
Price
From $39/month, 14-day trial
On this page
What you can read and change in Google Tag ManagerHow a GTM change runsThere is no dry run for GTM writesWhat still needs a personOther Google Tag Manager MCP serversSet up the Google Tag Manager MCPGoogle Tag Manager prompts to tryPlan limitsFAQRelated

What you can read and change in Google Tag Manager

All actions run through the gtm_native_action gateway. Action list checked in Whathead's code on 18 Nov 2026.
AreaReadChange
Accounts and usersAccounts, user permissionsUpdate accounts, add, change or remove user permissions
ContainersContainers, install snippet, lookup by GTM-XXXX tag ID, destinationsCreate, update, combine or delete containers, move a tag ID, link a destination
WorkspacesWorkspaces, workspace status (changed entities and merge conflicts)Create, sync, bulk update, resolve conflicts, quick preview
Tags, triggers, variablesEvery entity, built-in variables, Google tag configsCreate, update, delete or revert; enable or disable built-in variables
Templates and foldersCustom templates, folders and their contentsCreate or import gallery templates, create folders, move entities into folders
VersionsLive version, latest version header, version historyCreate a version from a workspace, publish, set latest, delete or undelete
EnvironmentsEnvironmentsCreate, update, delete or reauthorize
Server containersClients, transformations, zonesCreate, update, delete or revert

How a GTM change runs

Google Tag Manager already separates drafts from production. Tags, triggers and variables are edited in a workspace, and nothing reaches your site until a container version is published. The MCP follows that model, so a typical change is: read the container, write the new entities into a workspace, read the workspace status, test in Preview, then create a version and publish it.

  • Writes are queued as jobs by default and return a job id. gtm_action_job_status reads the result, or pass wait_for_completion to wait.
  • Every write carries an idempotency key, so a retried call does not create a second tag or trigger.
  • Updates and publishes accept GTM's fingerprint, so a change fails instead of overwriting someone else's newer edit.
  • When Google's Tag Manager API quota is hit, Whathead returns a retry-after time instead of hammering the API.

There is no dry run for GTM writes

Most Whathead platform writes start as dry-run previews. GTM writes do not: each create, update, delete or publish call is a real Tag Manager API request. The protection comes from GTM's own workspace and from these limits:

  • gtm_audit_ops reads a container without writing and reports duplicate names, tags with no firing trigger, references to missing triggers or variables, paused tags and merge conflicts.
  • Connect https://www.whathead.com/mcp/read for a connector that can only read. Its gtm_native_read tool refuses writes before anything reaches Google.
  • GTM writes need the write:gtm scope on the connector, and only the Whathead workspace owner can run them.
  • Claude and ChatGPT ask before running a write tool unless you have set it to always allow. Do not set GTM writes to always allow.

What still needs a person

The assistant removes the form-filling. It does not remove the judgment.

  • Testing in Preview mode (Tag Assistant) on the real site before you publish. The API cannot click through your checkout.
  • Consent settings on each tag and the consent banner itself. Which tags may fire before consent is a legal and business decision.
  • Naming conventions, so the next person can read the container.
  • The decision to publish. Ask for the workspace status and read it before you approve the publish call.

Other Google Tag Manager MCP servers

Checked 18 Nov 2026. We found no official Google Tag Manager MCP server from Google.
Stape google-tag-manager-mcp-serverWhathead
HostingHosted at gtm-mcp.stape.io/mcp, or a local CLI with your own credentialsHosted at www.whathead.com/mcp
CodeOpen source, Apache-2.0Hosted service, source not public
GTM coverage20 GTM tools, per its README106 Tag Manager API v2 actions plus a read-only audit
Other platformsGTM onlyGA4, Search Console and 12 ad platforms in the same chat

Set up the Google Tag Manager MCP

  1. Connect GTM in Whathead

    In Integrations, connect Google Tag Manager with the Google account that can edit your containers.

  2. Add Whathead to your assistant

    Claude: Settings, Connectors, add a custom connector with https://www.whathead.com/mcp. ChatGPT: a developer-mode connector with the same URL. Cursor: the URL plus a bearer token minted in Whathead.

  3. Start with a read

    Ask the assistant to look up your container by its GTM-XXXX ID and list its tags, triggers and variables, or run the container audit.

  4. Make changes in a workspace

    Ask for the new tag, trigger and variable, read the workspace status, test in Preview, and only then ask for a version and publish.

Google Tag Manager prompts to try

  • Look up container GTM-XXXXXXX and list every tag with its type, firing trigger and consent setting.

  • Audit the Default Workspace of GTM-XXXXXXX and explain each finding in plain language.

  • Which tags fire on All Pages, and are any two of them loading the same pixel?

  • Create a Data Layer Variable for ecommerce.transaction_id, a Custom Event trigger for purchase, and a GA4 event tag that uses both. Do not publish.

  • Show me the workspace status: every entity that changed since the live version.

  • Compare the live version with the latest version and list what changed.

  • Move every tag whose name starts with "Meta" into a folder called Meta.

  • Create a version named "GA4 purchase event" from this workspace and publish it after I confirm.

Plan limits

GTM calls share the monthly MCP allowance with your ad platforms: MCP Actions ($39) with 1,500 reads and 100 writes, Operator Bundle ($65) with 4,000 and 250, Agency ($249) with 15,000 and 750. Creating a tag, a trigger and a variable, then a version and a publish, uses 5 writes. All plans start with a 14-day trial.

Frequently asked questions

Is there an official Google Tag Manager MCP?

We found none from Google as of 18 November 2026. Google publishes an official MCP server for Google Analytics, and Stape maintains an open-source GTM MCP server.

Can the assistant publish my container?

Yes, if your Google account can publish and the connector has write access. Publishing is a separate call after a version is created, so ask for the workspace status first and confirm the publish yourself.

Does it work with server-side GTM?

Yes. Server containers use the same API, and the MCP covers their clients, transformations, tags, triggers and variables. Hosting the tagging server itself is outside Whathead.

Can it set up consent mode?

It can read and set the consent settings on each tag. Choosing a consent banner and deciding which tags wait for consent stays with you.

Can I connect it without write access?

Yes. Add https://www.whathead.com/mcp/read instead of /mcp. That connector lists only read tools and refuses GTM writes.

Related

  • GA4 MCP
  • Server-side tracking
  • Meta Ads MCP
  • Connect Claude to GA4 and Search Console
  • All platforms on the MCP server
  • Paid media tracking QA (blog)blog.whathead.com
  • Connect your assistant (docs)docs.whathead.com
  • Pricing

Run it from one workspace

Every plan starts with a 14-day free trial. Only successful live work is metered.

Start a 14-day trialCompare plans

Sources

  1. Google: Tag Manager API v2 reference (developers.google.com)
  2. Google: Tag Manager API limits and quotas (developers.google.com)
  3. Google: Consent mode in Tag Manager (support.google.com)
  4. Stape: google-tag-manager-mcp-server on GitHub (github.com)
Whathead© 2026 Whathead. Multi-platform ad operations and an Ads MCP server.
Product
PricingMCP serverMulti-platform ad managementCross-platform transferAd anomaly detectionBudget pacingServer-side trackingGoogle Sheets add-onLooker Studio connector
MCP servers
Meta Ads MCPGoogle Ads MCPTikTok Ads MCPSnapchat Ads MCPLinkedIn Ads MCPX Ads MCPReddit Ads MCPMicrosoft Ads MCPAmazon Ads MCPApple Ads MCPDV360 MCPCriteo MCPGA4 MCPGoogle Tag Manager MCPSearch Console MCPShopify MCP
Compare
Whathead vs Meta’s official MCPPipeboard alternativeSupermetrics alternativeWindsor.ai alternativeMadgicx alternativeMarkifact alternativeRevealbot (Birch) alternativeRyze AI alternative
Resources
BlogDocsAboutWhathead factsSupportContact
Legal
Terms of ServicePrivacy PolicyRefundsSecurity & DataLog in