Google Tag Manager MCP

English | Русский

A1 Google Tag Manager MCP lets an AI app inspect and manage Google Tag Manager containers in plain language. See what fires on a page, work with tags, triggers and variables in a draft workspace, then deliberately compile and publish a version when you are ready.

It connects to the Google Tag Manager API v2 through your Google account. The difference from asking an AI to guess a GTM setup is that it works with the actual container, workspace and version you choose.

• 25 tools. 10 operations only read GTM data; 4 create drafts or change built-in variables; 5 can alter, delete, compile or publish live configuration.
• Connects from the conversation. Say "connect Google Tag Manager": the server walks you through the OAuth client, catches Google's redirect on 127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.
• Draft first. Tags, triggers and variables are created in a workspace. Publishing is a separate, explicitly destructive operation.
• Quota-aware. GTM permits 0.25 requests per second per project; the server spaces requests by at least 4.2 seconds instead of overwhelming the API.
• Your Google access. The server uses your OAuth credentials and requests only the Tag Manager scopes needed for reading, editing, versioning and publishing.

Start with a read-only question:

Which tags in my containers fire on the page-view trigger?

Connect the server · Explore use cases · Open technical documentation

See it work in a minute

You: List my GTM containers and show which tags fire on page view.

Assistant: Lists the containers, their workspaces, relevant triggers and the tags attached to them. Nothing changes.

You: In the Default Workspace of GTM-ABC123, prepare a GA4 configuration tag for measurement ID G-XXXXXXX on all pages.

Assistant: Shows the workspace, proposed tag and trigger configuration, then asks for confirmation before creating the draft.

You: Confirm the draft.

Assistant: Creates the tag in the workspace. It does not publish the container; compiling and publishing a version remains a separate step.

Contents

• Quick start
• What you can ask it to do
• How GTM changes are connected
• What can change
• Getting access
• Configuration
• Data and telemetry
• Limits and background work
• Technical documentation
• Support

Quick start

You need Node.js 20+ and a Google account. Credentials are not required at install time — the server connects from the conversation.

1. Add the server to your AI app.
2. Say "connect Google Tag Manager": the assistant walks you through creating the OAuth client and approving access without editing config files.
3. Start with the read-only question above.

codex mcp add google-tagmanager \
  -- npx -y mcp-google-tagmanager@latest

codex mcp list

claude mcp add \
  --transport stdio \
  --scope user \
  google-tagmanager \
  -- npx -y mcp-google-tagmanager@latest

claude mcp list

{
  "mcpServers": {
    "google-tagmanager": {
      "command": "npx",
      "args": ["-y", "mcp-google-tagmanager@latest"]
    }
  }
}

{
  "mcpServers": {
    "google-tagmanager": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "mcp-google-tagmanager@latest"]
    }
  }
}

{
  "servers": {
    "google-tagmanager": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "mcp-google-tagmanager@latest"]
    }
  }
}

What you can ask it to do

Understand the current setup

• List the GTM accounts and containers I can access.
• Which tags fire on page view in this workspace?
• Show the trigger and variable configuration for this tag.
• Which built-in variables are enabled?

Prepare tracking changes in a draft

• Create a workspace for the checkout tracking change.
• Prepare a GA4 tag and a trigger for a specific event.
• Enable the click variables needed for this trigger.
• Update this tag after showing me the complete replacement configuration.

Release a version deliberately

• Compile this workspace into a version named April release.
• Show the compiler errors, if any.
• Publish version 42 after I confirm the version and its changes.

How GTM changes are connected

GTM has a clear release path:

1. An account contains one or more containers.
2. A container has workspaces for draft changes.
3. Tags, triggers and variables belong to a workspace.
4. Compiling a workspace creates a container version and removes the source workspace. GTM provides a replacement workspace.
5. Publishing makes a selected container version live.

This server can inspect each step. It does not treat a draft as a release: version creation and publishing are separate operations.

What can change

The AI client decides how it asks for confirmation. The server marks read-only, write and destructive operations so the client can distinguish inspection from a real change.

Getting access

Google Tag Manager requires OAuth 2.0; an API key is not enough. There are two ways in, and the first one needs no configuration files.

Connect from the chat (recommended)

Say "connect Google Tag Manager" and the assistant runs the flow with you: