Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Google Tag Manager MCP

NPM · MCP-GOOGLE-TAGMANAGER · SCANNED SEP 20

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

0 this week 82 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2823 tokens (~148/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

npm · mcp-google-tagmanager

# add to Claude Code
claude mcp add a1-x-tech-mcp-google-tagmanager -- npx -y mcp-google-tagmanager
// .cursor/mcp.json
{
  "mcpServers": {
    "a1-x-tech-mcp-google-tagmanager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-tagmanager"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "a1-x-tech-mcp-google-tagmanager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-tagmanager"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add a1-x-tech-mcp-google-tagmanager --command npx --arg -y --arg mcp-google-tagmanager
# ~/.hermes/config.yaml
mcp_servers:
  a1-x-tech-mcp-google-tagmanager:
    command: "npx"
    args: ["-y", "mcp-google-tagmanager"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "a1-x-tech-mcp-google-tagmanager": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-google-tagmanager"
      ]
    }
  }
}
# add to Vellum
assistant mcp add a1-x-tech-mcp-google-tagmanager -t stdio -c npx -a -y mcp-google-tagmanager
// mcp.json
{
  "mcpServers": {
    "a1-x-tech-mcp-google-tagmanager": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-tagmanager"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +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.

  • 18 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +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.

  • 14 Sept 26 +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.

  • 12 Sept 26 +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.

  • 10 Sept 26 +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.

  • 7 Sept 26 +1

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

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/mcp-google-tagmanager@1.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 19 exposed · ~2,458 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_container ~124

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.

NameTypeReqDescription
account_idstringyesGTM account id (string).
namestringyesDisplay name of the new container.
usage_contextarrayyesUsage contexts, e.g. ["web"]. Other documented values: androidSdk5, iosSdk5, server.

No output schema declared.

No examples provided.

create_entity ~185

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.

NameTypeReqDescription
account_idstringyesGTM account id (string).
bodyobjectyesThe resource JSON to create (name, type, parameter, and for tags firingTriggerId).
container_idstringyesContainer id (string).
entity_typestringyesWhich collection to create in.
workspace_idstringyesWorkspace id (string).

No output schema declared.

No examples provided.

create_version ~199

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).

NameTypeReqDescription
account_idstringyesGTM account id (string).
container_idstringyesContainer id (string).
namestringVersion display name.
notesstringVersion notes (changelog entry).
workspace_idstringyesWorkspace id (string) to compile. This workspace is deleted afterwards.

No output schema declared.

No examples provided.

create_workspace ~108

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.

NameTypeReqDescription
account_idstringyesGTM account id (string).
container_idstringyesContainer id (string).
descriptionstringOptional description of what this workspace changes.
namestringyesDisplay name of the new workspace.

No output schema declared.

No examples provided.

delete_entity ~78

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

NameTypeReqDescription
pathstringyesAPI-relative resource path as returned in the resource's own "path" field, e.g. "accounts/1/containers/2/workspaces/3/variables/7".

No output schema declared.

No examples provided.

get_account ~57

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

NameTypeReqDescription
account_idstringyesGTM account id (string), e.g. from list_accounts.

No output schema declared.

No examples provided.

get_container ~74

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

NameTypeReqDescription
account_idstringyesGTM account id (string).
container_idstringyesContainer id (string), e.g. from list_containers.

No output schema declared.

No examples provided.

get_resource ~109

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).

NameTypeReqDescription
pathstringyesAPI-relative resource path as returned in the resource's own "path" field, e.g. "accounts/1/containers/2/workspaces/3/tags/4".

No output schema declared.

No examples provided.

get_workspace ~75

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

NameTypeReqDescription
account_idstringyesGTM account id (string).
container_idstringyesContainer id (string).
workspace_idstringyesWorkspace id (string), e.g. from list_workspaces.

No output schema declared.

No examples provided.

list_accounts ~90

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.

NameTypeReqDescription
page_tokenstringPagination token from a previous response's nextPageToken. Omit for the first page.

No output schema declared.

No examples provided.

list_containers ~96

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

NameTypeReqDescription
account_idstringyesGTM account id (string).
page_tokenstringPagination token from a previous response's nextPageToken. Omit for the first page.

No output schema declared.

No examples provided.

list_tags ~144

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 }.

NameTypeReqDescription
account_idstringyesGTM account id (string).
container_idstringyesContainer id (string).
page_tokenstringPagination token from a previous response's nextPageToken. Omit for the first page.
workspace_idstringyesWorkspace id (string), e.g. from list_workspaces.

No output schema declared.

No examples provided.

list_triggers ~132

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 }.

NameTypeReqDescription
account_idstringyesGTM account id (string).
container_idstringyesContainer id (string).
page_tokenstringPagination token from a previous response's nextPageToken. Omit for the first page.
workspace_idstringyesWorkspace id (string), e.g. from list_workspaces.

No output schema declared.

No examples provided.

list_variables ~141

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 }.

NameTypeReqDescription
account_idstringyesGTM account id (string).
container_idstringyesContainer id (string).
page_tokenstringPagination token from a previous response's nextPageToken. Omit for the first page.
workspace_idstringyesWorkspace id (string), e.g. from list_workspaces.

No output schema declared.

No examples provided.

list_workspaces ~124

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.

NameTypeReqDescription
account_idstringyesGTM account id (string).
container_idstringyesContainer id (string).
page_tokenstringPagination token from a previous response's nextPageToken. Omit for the first page.

No output schema declared.

No examples provided.

manage_built_in_variables ~176

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.

NameTypeReqDescription
account_idstringyesGTM account id (string).
actionstringyesWhat to do.
container_idstringyesContainer id (string).
typesarrayBuilt-in variable types to enable/disable (required for those actions), e.g. ["pageUrl", "clickText"]. Ignored for "list".
workspace_idstringyesWorkspace id (string).

No output schema declared.

No examples provided.

publish_version ~194

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 }).

NameTypeReqDescription
account_idstringyesGTM account id (string).
actionstringyesWhat to do.
container_idstringyesContainer id (string).
fingerprintstringThe version's last-seen fingerprint ("publish" only), for optimistic-concurrency safety.
version_idstringContainer version id (string). Required for "publish" and "get"; ignored for "live".

No output schema declared.

No examples provided.

raw_request ~193

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.

NameTypeReqDescription
bodyobjectJSON request body (POST/PUT).
methodstringHTTP method. Defaults to GET.
pathstringyesAPI path relative to /tagmanager/v2/, e.g. "accounts/1/containers/2/version_headers".
queryobjectQuery parameters; use an array for repeated keys, e.g. { "type": ["pageUrl", "event"] }.

No output schema declared.

No examples provided.

update_entity ~159

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.

NameTypeReqDescription
bodyobjectyesThe complete replacement resource JSON.
fingerprintstringThe fingerprint from the last read of this resource; the update fails if it is stale.
pathstringyesAPI-relative resource path as returned in the resource's own "path" field, e.g. "accounts/1/containers/2/workspaces/3/triggers/5".

No output schema declared.

No examples provided.

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 82 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 19 tools: list_accounts, get_account, list_containers, get_container, create_container, and 14 more. Their descriptions and schemas cost roughly 2,458 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.