How do I install Google Tag Manager MCP?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Google Tag Manager MCP need an API key?

The publisher lists these environment variables: GOOGLE_TAGMANAGER_CLIENT_ID, GOOGLE_TAGMANAGER_CLIENT_SECRET, GOOGLE_TAGMANAGER_REFRESH_TOKEN, GOOGLE_TAGMANAGER_ACCESS_TOKEN, GOOGLE_TAGMANAGER_OAUTH_PORT, GOOGLE_TAGMANAGER_API_BASE, GOOGLE_TAGMANAGER_TIMEOUT_MS, GOOGLE_TAGMANAGER_MAX_RETRIES, GOOGLE_TAGMANAGER_MIN_INTERVAL_MS.

What transport does Google Tag Manager MCP use?

Google Tag Manager MCP runs locally over stdio.

When was Google Tag Manager MCP last checked?

Last checked 2026-11-11. MCP server for the Google Tag Manager API v2: containers, workspaces, tags, triggers, publishing.

Google Tag Manager MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Credentials from the publisher

GOOGLE_TAGMANAGER_CLIENT_ID — Google OAuth client id (refresh-token flow).
GOOGLE_TAGMANAGER_CLIENT_SECRET — Google OAuth client secret (refresh-token flow). Treat it as a secret.
GOOGLE_TAGMANAGER_REFRESH_TOKEN — Google OAuth refresh token; exchanged for access tokens automatically. Treat it as a secret.
GOOGLE_TAGMANAGER_ACCESS_TOKEN — Ready-made OAuth access token (~1h lifetime). Alternative to the client-id/secret/refresh-token trio.
GOOGLE_TAGMANAGER_OAUTH_PORT — Fixed port for the loopback listener of the in-chat login (127.0.0.1 + PKCE). Set it when the client runs over SSH port forwarding; otherwise a free port is picked per login.
GOOGLE_TAGMANAGER_API_BASE — API root host override.
GOOGLE_TAGMANAGER_TIMEOUT_MS — Per-request timeout in milliseconds.
GOOGLE_TAGMANAGER_MAX_RETRIES — Retries on transient errors (429, quota 403, and 5xx/network for reads).
GOOGLE_TAGMANAGER_MIN_INTERVAL_MS — Minimum spacing between API requests, for the 0.25 QPS quota.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1GOOGLE_TAGMANAGER_CLIENT_ID=<value> GOOGLE_TAGMANAGER_CLIENT_SECRET=<secret> GOOGLE_TAGMANAGER_REFRESH_TOKEN=<secret> GOOGLE_TAGMANAGER_ACCESS_TOKEN=<secret> GOOGLE_TAGMANAGER_OAUTH_PORT=<value> GOOGLE_TAGMANAGER_API_BASE=<value> GOOGLE_TAGMANAGER_TIMEOUT_MS=<value> GOOGLE_TAGMANAGER_MAX_RETRIES=<value> GOOGLE_TAGMANAGER_MIN_INTERVAL_MS=<value> claude mcp add io.github.a1-x-tech-mcp-google-tagmanager -- npx -y mcp-google-tagmanager@1.3.2

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.a1-x-tech-mcp-google-tagmanager": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "GOOGLE_TAGMANAGER_CLIENT_ID": "<value>",11        "GOOGLE_TAGMANAGER_CLIENT_SECRET": "<secret>",12        "GOOGLE_TAGMANAGER_REFRESH_TOKEN": "<secret>",13        "GOOGLE_TAGMANAGER_ACCESS_TOKEN": "<secret>",14        "GOOGLE_TAGMANAGER_OAUTH_PORT": "<value>",15        "GOOGLE_TAGMANAGER_API_BASE": "<value>",16        "GOOGLE_TAGMANAGER_TIMEOUT_MS": "<value>",17        "GOOGLE_TAGMANAGER_MAX_RETRIES": "<value>",18        "GOOGLE_TAGMANAGER_MIN_INTERVAL_MS": "<value>"19      }20    }21  }22}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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.

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.

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

In the app:

Open Settings → MCP servers.
Select Add server.
Choose STDIO, then enter npx -y mcp-google-tagmanager@latest and the three environment variables below.

Variable	Value
`GOOGLE_TAGMANAGER_CLIENT_ID`	Your Google OAuth client ID
`GOOGLE_TAGMANAGER_CLIENT_SECRET`	Your Google OAuth client secret
`GOOGLE_TAGMANAGER_REFRESH_TOKEN`	Your Google OAuth refresh token

Select Save, then Restart.

From the command line:

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

codex mcp list

Codex MCP documentation

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

claude mcp list

Claude Code MCP documentation

The current official path is Settings → Extensions. For a custom desktop extension, open Advanced settings → Extension Developer → Install Extension…, select a .mcpb file and follow the prompts.

This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:

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

In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.

Claude Desktop MCP documentation

Add a user-level server to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:

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

Cursor MCP documentation

Run MCP: Open User Configuration from the Command Palette and add:

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

Check it with MCP: List Servers.

VS Code MCP documentation

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:

An account contains one or more containers.
A container has workspaces for draft changes.
Tags, triggers and variables belong to a workspace.
Compiling a workspace creates a container version and removes the source workspace. GTM provides a replacement workspace.
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

Operation	What happens	Confirmation boundary
List accounts, containers, workspaces, tags, triggers, variables and versions	Reads GTM configuration	No change
Create a container or workspace	Adds a new GTM object	Changes GTM
Create a tag, trigger or variable	Adds a draft object to a workspace	Changes a draft workspace
Enable or disable built-in variables	Changes the workspace configuration	Changes a draft workspace
Update a tag, trigger or variable	Replaces the complete resource, protected by its fingerprint	Potentially destructive
Delete a tag, trigger or variable	Removes the selected object	Destructive
Compile a workspace	Creates a version and deletes the source workspace	Destructive
Publish a version	Makes a selected version live	Destructive
Raw API request	Can call API methods without a dedicated tool	Potentially destructive

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:

setup_instructions prints the checklist: create or select a Google Cloud project, enable Tag Manager API, configure the consent screen and create a Desktop app OAuth client.
Download that client's JSON ("Download JSON") and give the assistant its path — set_client stores it owner-only. The secret never goes through the conversation.
start_login returns a Google consent link. Open it on this machine and approve; the code comes back to a one-shot listener on 127.0.0.1 (PKCE), never through the chat.
finish_login exchanges the code and saves the tokens to ~/.config/mcp-google-tagmanager/credentials.json (mode 0600) and verifies them with a real Tag Manager API call — so an API that is still switched off is caught right there.

The tokens are re-read on every call, so the connection works immediately — no restart of the AI app. auth_status shows what is connected, logout revokes and deletes it.

Environment variables (CI, unattended installs)

Create or select a Google Cloud project and enable the Tag Manager API. A project without that API enabled receives no quota.
Configure the OAuth consent screen and create an OAuth client. A Desktop app client is suitable for local use.
Authorize your Google account and obtain a refresh token. The OAuth 2.0 Playground can do this if you enable Use your own OAuth credentials.

Request these scopes together:

https://www.googleapis.com/auth/tagmanager.readonly
https://www.googleapis.com/auth/tagmanager.edit.containers
https://www.googleapis.com/auth/tagmanager.edit.containerversions
https://www.googleapis.com/auth/tagmanager.publish

The scopes are separate: reading, editing, compiling versions and publishing each need their corresponding permission. Treat the client secret and refresh token as passwords.

Configuration

Every variable is optional — with none of them the server connects from the chat.

Variable	Required	Description
`GOOGLE_TAGMANAGER_CLIENT_ID`	No*	OAuth client ID.
`GOOGLE_TAGMANAGER_CLIENT_SECRET`	No*	OAuth client secret.
`GOOGLE_TAGMANAGER_REFRESH_TOKEN`	No*	OAuth refresh token.
`GOOGLE_TAGMANAGER_ACCESS_TOKEN`	No*	Short-lived alternative to the OAuth trio.
`GOOGLE_TAGMANAGER_OAUTH_PORT`	No	Fixed loopback port for the in-chat login; useful over SSH port forwarding.
`GOOGLE_TAGMANAGER_API_BASE`	No	Tag Manager API base URL override.
`GOOGLE_TAGMANAGER_TIMEOUT_MS`	No	Per-request timeout; default `60000` ms.
`GOOGLE_TAGMANAGER_MAX_RETRIES`	No	Maximum retries on temporary failures; default `3`.
`GOOGLE_TAGMANAGER_MIN_INTERVAL_MS`	No	Minimum request spacing; default `4200` ms.

* Provide either the OAuth trio or an access token. Access tokens expire in about an hour and are not refreshed automatically.

Data and telemetry

The server runs locally and sends GTM API requests and OAuth refresh requests to Google. Its anonymous telemetry contains a random installation ID, package version, AI client and Node.js/operating-system versions, and tool names. It does not send OAuth tokens, GTM data, tool arguments or prompts.

Disable telemetry for A1 MCP servers with:

ASKADS_TELEMETRY=0

Limits and background work

GTM is rate-limited. The API allows 0.25 requests per second per project, so the server serializes calls at least 4.2 seconds apart. Broad audits can therefore take time.
Temporary limits are retried carefully. 429 and Google quota 403 responses use exponential backoff and Retry-After. Reads retry after network and 5xx failures; writes are not replayed after an uncertain failure.
There is no background monitoring. The server runs only when your AI app calls it. If the app supports scheduled tasks, it can periodically inspect a container or its live version.
A workspace disappears when compiled. Before calling create_version, save anything you need from the workspace and inspect the returned replacement workspace path.

Technical documentation

MCP capability catalog — task-oriented pages for every tool.
All tools and inputs
Development documentation
Publishing documentation
Google Tag Manager API v2 reference

Support

Found a bug or need a scenario? Create an issue or write in Telegram.

Google Tag Manager MCP

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Google Tag Manager MCP?

Does Google Tag Manager MCP need an API key?

What transport does Google Tag Manager MCP use?

When was Google Tag Manager MCP last checked?

Documentation

Google Tag Manager MCP

See it work in a minute

Contents

Quick start

What you can ask it to do

Understand the current setup

Prepare tracking changes in a draft

Release a version deliberately

How GTM changes are connected

What can change

Getting access

Connect from the chat (recommended)

Environment variables (CI, unattended installs)

Configuration

Data and telemetry

Limits and background work

Technical documentation

Support