# Google Tag Manager MCP (npm · mcp-google-tagmanager)

MCP server for the Google Tag Manager API v2: containers, workspaces, tags, triggers, publishing.

- Trust score: 83/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `mcp-google-tagmanager`: 83/100 (this document), [markdown](https://verifymcp.io/servers/a1-x-tech-mcp-google-tagmanager/mcp-google-tagmanager.md), [page](https://verifymcp.io/servers/a1-x-tech-mcp-google-tagmanager/mcp-google-tagmanager)

## Channel facts

- Registry: `npm`
- Package: `mcp-google-tagmanager`
- Version: `1.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 97 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3398 tokens (~135/item across 25 items; 25 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Google Tag Manager MCP server?

Google Tag Manager MCP runs locally as an npm package, launched with npx -y mcp-google-tagmanager. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add a1-x-tech-mcp-google-tagmanager -- npx -y mcp-google-tagmanager
```

### Cursor

```json
{
  "mcpServers": {
    "a1-x-tech-mcp-google-tagmanager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-tagmanager"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "a1-x-tech-mcp-google-tagmanager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-tagmanager"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add a1-x-tech-mcp-google-tagmanager -- npx -y mcp-google-tagmanager
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "a1-x-tech-mcp-google-tagmanager": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-google-tagmanager"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add a1-x-tech-mcp-google-tagmanager --command npx --arg -y --arg mcp-google-tagmanager
```

### Hermes

```yaml
mcp_servers:
  a1-x-tech-mcp-google-tagmanager:
    command: "npx"
    args: ["-y", "mcp-google-tagmanager"]
```

### Netclaw

```json
{
  "McpServers": {
    "a1-x-tech-mcp-google-tagmanager": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-google-tagmanager"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add a1-x-tech-mcp-google-tagmanager -t stdio -c npx -a -y mcp-google-tagmanager
```

### Other

```json
{
  "mcpServers": {
    "a1-x-tech-mcp-google-tagmanager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-tagmanager"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 83, +1)

- [security regression] Stability: 0.83 → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Schema quality: 2823 → 3398
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 1.1.0 → 1.2.0

### 2026-09-19 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 81, −3)

- [functional] Stability: pass → 0.80

### 2026-09-17 (score 84, 0)

- [security] Stability: 0.97 → pass

### 2026-09-16 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (25)

### `auth_status` (~81 tokens)

Google connection status

Shows whether this server is connected to Google: token presence and source (env variables or a stored in-chat login), expiry, the Google account email, granted vs missing OAuth scopes, where the credentials file lives and where the OAuth client comes from. Makes no network calls and never returns the token itself. Call it first when other tools report the server is not connected.

### `setup_instructions` (~109 tokens)

Setup instructions

Step-by-step checklist for connecting this server to Google: creating a Google Cloud project and a Desktop-app OAuth client, publishing the consent screen (mandatory — Testing-mode refresh tokens die after 7 days), downloading the client JSON and handing its PATH to set_client. Works without any credentials; the checklist shortens to 'enable the API + log in' when an OAuth client is already configured (one client serves the whole mcp-google-* line). Never asks the user to paste secrets into the chat.

### `set_client` (~111 tokens)

Save the OAuth client

Saves the OAuth client credentials from the JSON file downloaded from Google Cloud Console ('Download JSON' on a Desktop-app client). Pass the file PATH — the secret must never be pasted into the chat. The client is stored once in the shared ~/.config/mcp-google-auth/client.json (owner-only) and reused by every mcp-google-* server; tokens stay per-server. After this, call start_login.

Input parameters:

- `path` (string, required): Absolute path to the client_secret_*.json file downloaded from Google Cloud Console.

### `start_login` (~114 tokens)

Start the Google login

First step of connecting from the chat, without editing config files or restarting the client. Returns authorizeUrl — show it to the user as a clickable link and ask them to open it in the browser ON THIS MACHINE, pick the Google account and approve access. A one-shot listener on 127.0.0.1 catches Google's redirect; the code is exchanged locally and never passes through the chat. Does not open the browser itself. The attempt lives 10 minutes; when the browser shows the success page, call finish_login.

### `finish_login` (~116 tokens)

Finish the Google login

Second step: confirms the browser consent finished, saves the tokens to an owner-only file and verifies the login with a read-only identity call, returning the account email and the granted scopes. After success every tool works immediately — no client restart. If the user granted only part of the requested permissions, the login is still saved and missingScopes lists what will not work. Logging in under a different Google account replaces the previous login (its refresh token is revoked best-effort) and the response carries previousAccountEmail so the change never goes unnoticed.

### `logout` (~62 tokens)

Disconnect from Google

Revokes the stored token at Google (oauth2.googleapis.com/revoke) and deletes the local credentials file. Tokens supplied via env variables are NOT touched — remove them from the MCP client config manually; envTokenStillSet in the response says whether any are still in effect.

### `list_accounts` (~90 tokens)

List GTM accounts

Lists all Google Tag Manager accounts the authorized user can access. Returns { account: [{ accountId, name, path, fingerprint }], nextPageToken }. All ids are strings. This is the entry point: every other tool needs an accountId (or a path) from here.

Input parameters:

- `page_token` (string): Pagination token from a previous response's nextPageToken. Omit for the first page.

### `get_account` (~57 tokens)

Get a GTM account

Gets one Google Tag Manager account by id. Returns the Account resource: { accountId, name, path, fingerprint, shareData }.

Input parameters:

- `account_id` (string, required): GTM account id (string), e.g. from list_accounts.

### `list_containers` (~96 tokens)

List containers

Lists the containers of a GTM account. Returns { container: [{ containerId, name, publicId (e.g. GTM-XXXXXX), usageContext, path, fingerprint, tagManagerUrl }], nextPageToken }.

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `page_token` (string): Pagination token from a previous response's nextPageToken. Omit for the first page.

### `get_container` (~74 tokens)

Get a container

Gets one container by account id + container id. Returns the Container resource including publicId (the GTM-XXXXXX snippet id), usageContext and fingerprint.

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `container_id` (string, required): Container id (string), e.g. from list_containers.

### `create_container` (~124 tokens)

Create a container

Creates a new container in a GTM account. usage_context declares the platform, e.g. ["web"]; other values include androidSdk5, iosSdk5, server. Returns the created Container with its server-assigned containerId and publicId. Requires the tagmanager.edit.containers scope.

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `name` (string, required): Display name of the new container.
- `usage_context` (array, required): Usage contexts, e.g. ["web"]. Other documented values: androidSdk5, iosSdk5, server.

### `list_workspaces` (~124 tokens)

List workspaces

Lists the workspaces of a container. Returns { workspace: [{ workspaceId, name, description, path, fingerprint }], nextPageToken }. Workspaces are mandatory in GTM v2: every tag/trigger/variable operation needs a workspaceId, and a "Default Workspace" always exists — call this first.

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `container_id` (string, required): Container id (string).
- `page_token` (string): Pagination token from a previous response's nextPageToken. Omit for the first page.

### `get_workspace` (~75 tokens)

Get a workspace

Gets one workspace by account id + container id + workspace id. Returns the Workspace resource with its fingerprint.

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `container_id` (string, required): Container id (string).
- `workspace_id` (string, required): Workspace id (string), e.g. from list_workspaces.

### `create_workspace` (~108 tokens)

Create a workspace

Creates a new workspace in a container — an isolated draft where tags, triggers and variables are edited before being compiled into a version. Returns the created Workspace with its server-assigned workspaceId. Requires the tagmanager.edit.containers scope.

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `container_id` (string, required): Container id (string).
- `description` (string): Optional description of what this workspace changes.
- `name` (string, required): Display name of the new workspace.

### `list_tags` (~144 tokens)

List tags

Lists the tags of a workspace. Returns { tag: [{ tagId, name, type (e.g. html, gaawe), parameter: [{ type, key, value, list, map }], firingTriggerId, blockingTriggerId, paused, path, fingerprint, tagManagerUrl }], nextPageToken }.

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `container_id` (string, required): Container id (string).
- `page_token` (string): Pagination token from a previous response's nextPageToken. Omit for the first page.
- `workspace_id` (string, required): Workspace id (string), e.g. from list_workspaces.

### `list_triggers` (~132 tokens)

List triggers

Lists the triggers of a workspace. Returns { trigger: [{ triggerId, name, type (e.g. pageview, click, customEvent), filter/customEventFilter (conditions of { type, parameter }), path, fingerprint }], nextPageToken }.

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `container_id` (string, required): Container id (string).
- `page_token` (string): Pagination token from a previous response's nextPageToken. Omit for the first page.
- `workspace_id` (string, required): Workspace id (string), e.g. from list_workspaces.

### `list_variables` (~141 tokens)

List variables

Lists the user-defined variables of a workspace (built-in variables live in manage_built_in_variables). Returns { variable: [{ variableId, name, type (e.g. v = data layer, jsm = custom JS, c = constant), parameter, path, fingerprint }], nextPageToken }.

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `container_id` (string, required): Container id (string).
- `page_token` (string): Pagination token from a previous response's nextPageToken. Omit for the first page.
- `workspace_id` (string, required): Workspace id (string), e.g. from list_workspaces.

### `get_resource` (~109 tokens)

Get any resource by path

Generic getter for any GTM resource by its API-relative path — tags, triggers, variables, versions, containers, workspaces. Prefer echoing the `path` field from a previous response over assembling the string yourself. Returns the full resource JSON including its current fingerprint (needed for update_entity).

Input parameters:

- `path` (string, required): API-relative resource path as returned in the resource's own "path" field, e.g. "accounts/1/containers/2/workspaces/3/tags/4".

### `create_entity` (~185 tokens)

Create a tag, trigger or variable

Creates a tag, trigger or variable in a workspace. `body` is the resource JSON: minimally { name, type } plus type-specific parameter entries; tags also take firingTriggerId (array of trigger id strings). Example tag body: { "name": "GA4 event", "type": "gaawe", "parameter": [...], "firingTriggerId": ["12"] }. Returns the created resource with its server-assigned id and fingerprint. Requires the tagmanager.edit.containers scope.

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `body` (object, required): The resource JSON to create (name, type, parameter, and for tags firingTriggerId).
- `container_id` (string, required): Container id (string).
- `entity_type` (string, required): Which collection to create in.
- `workspace_id` (string, required): Workspace id (string).

### `update_entity` (~159 tokens)

Update a tag, trigger or variable

Updates a tag, trigger or variable by its API path. PUT semantics: this is a FULL REPLACE, not a patch — fetch the current resource with get_resource, modify it, and send the whole object back. Pass the resource's last-seen fingerprint for optimistic-concurrency safety; a mismatch fails the request. Requires the tagmanager.edit.containers scope.

Input parameters:

- `body` (object, required): The complete replacement resource JSON.
- `fingerprint` (string): The fingerprint from the last read of this resource; the update fails if it is stale.
- `path` (string, required): API-relative resource path as returned in the resource's own "path" field, e.g. "accounts/1/containers/2/workspaces/3/triggers/5".

### `delete_entity` (~78 tokens)

Delete a tag, trigger or variable

Deletes a tag, trigger or variable by its API path. The response is empty on success. Requires the tagmanager.edit.containers scope.

Input parameters:

- `path` (string, required): API-relative resource path as returned in the resource's own "path" field, e.g. "accounts/1/containers/2/workspaces/3/variables/7".

### `manage_built_in_variables` (~176 tokens)

List/enable/disable built-in variables

Manages a workspace's built-in variables (pageUrl, clickText, event, ...). These are toggles, not records: action "list" returns the currently enabled ones ({ builtInVariable: [...] }), "enable" and "disable" take `types` (BuiltInVariableType enum values) and switch them on/off. Enable/disable require the tagmanager.edit.containers scope.

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `action` (string, required): What to do.
- `container_id` (string, required): Container id (string).
- `types` (array): Built-in variable types to enable/disable (required for those actions), e.g. ["pageUrl", "clickText"]. Ignored for "list".
- `workspace_id` (string, required): Workspace id (string).

### `create_version` (~199 tokens)

Create a container version from a workspace

Compiles a workspace into an immutable Container Version (the unit that gets published). SIDE EFFECT: the source workspace is DELETED and replaced by a fresh one — the response's newWorkspacePath points to the replacement; use it for any further edits, or old workspace paths will 404. Returns { containerVersion (with containerVersionId and full tag/trigger/variable snapshots), syncStatus, newWorkspacePath }. A compile failure comes back as compilerError=true with HTTP 200 and is reported as an error. Requires the tagmanager.edit.containerversions scope (edit.containers is NOT sufficient).

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `container_id` (string, required): Container id (string).
- `name` (string): Version display name.
- `notes` (string): Version notes (changelog entry).
- `workspace_id` (string, required): Workspace id (string) to compile. This workspace is deleted afterwards.

### `publish_version` (~194 tokens)

Publish, inspect or fetch the live container version

Container-version operations. action "publish" pushes a version live (replacing the currently published one; requires the tagmanager.publish scope; version_id required, fingerprint recommended). action "get" fetches one version by version_id. action "live" fetches the currently published version of the container (no version_id needed). Publish responses can carry compilerError=true with HTTP 200 — reported as an error. Returns the ContainerVersion (publish wraps it as { containerVersion, compilerError }).

Input parameters:

- `account_id` (string, required): GTM account id (string).
- `action` (string, required): What to do.
- `container_id` (string, required): Container id (string).
- `fingerprint` (string): The version's last-seen fingerprint ("publish" only), for optimistic-concurrency safety.
- `version_id` (string): Container version id (string). Required for "publish" and "get"; ignored for "live".

### `raw_request` (~193 tokens)

Raw Tag Manager API call

Escape hatch to call any Google Tag Manager API v2 path directly, for endpoints without a dedicated tool (environments, folders, templates, zones, workspace :sync / :quick_preview, version_headers, ...). `path` is relative to /tagmanager/v2/, e.g. "accounts/1/containers/2/environments". `query` values may be arrays for repeated params. Requests go through the same OAuth, rate limiter and retries as every other tool.

Input parameters:

- `body` (object): JSON request body (POST/PUT).
- `method` (string): HTTP method. Defaults to GET.
- `path` (string, required): API path relative to /tagmanager/v2/, e.g. "accounts/1/containers/2/version_headers".
- `query` (object): Query parameters; use an array for repeated keys, e.g. { "type": ["pageUrl", "event"] }.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/a1-x-tech-mcp-google-tagmanager/mcp-google-tagmanager#diagnostics

## Score history

- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 81
- 2026-09-17: 84
- 2026-09-16: 84
- 2026-09-15: 83
- 2026-09-14: 83
- 2026-09-13: 82
- 2026-09-12: 82
- 2026-09-11: 81
- 2026-09-10: 81
- 2026-09-09: 80
- 2026-09-08: 80
- 2026-09-07: 80
- 2026-09-06: 79
- 2026-09-05: 79
- 2026-09-04: 78
- 2026-09-03: 78
- 2026-09-02: 77
- 2026-09-01: 77
- 2026-08-31: 76
- 2026-08-30: 76
- 2026-08-29: 75
- 2026-08-28: 75
- 2026-08-27: 74
- 2026-08-26: 74
- 2026-08-25: 69
- 2026-08-24: 69
- 2026-08-23: 69
- 2026-08-22: 69

## Common questions

### What is the Google Tag Manager MCP server?

Google Tag Manager MCP is listed in the public MCP registry as io.github.A1-x-Tech/mcp-google-tagmanager. MCP server for the Google Tag Manager API v2: containers, workspaces, tags, triggers, publishing. This page covers its npm package (mcp-google-tagmanager).

### Is the Google Tag Manager MCP server safe to use?

Google Tag Manager MCP scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Google Tag Manager MCP server expose?

Google Tag Manager MCP exposes 25 tools: auth_status, setup_instructions, set_client, start_login, finish_login, and 20 more. Their descriptions and schemas cost roughly 3,051 tokens of context every time the server is loaded.

### Is the Google Tag Manager MCP server still maintained?

Google Tag Manager MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Google Tag Manager MCP server under?

Google Tag Manager MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/mcp-google-tagmanager
- Socket report: https://socket.dev/npm/package/mcp-google-tagmanager
- Repository: https://github.com/A1-x-Tech/mcp-google-tagmanager
- Changelog RSS feed: https://verifymcp.io/servers/a1-x-tech-mcp-google-tagmanager/mcp-google-tagmanager.xml
- Changelog JSON feed: https://verifymcp.io/servers/a1-x-tech-mcp-google-tagmanager/mcp-google-tagmanager.json
- HTML version of this page: https://verifymcp.io/servers/a1-x-tech-mcp-google-tagmanager/mcp-google-tagmanager