Google Tag Manager MCP
Provides tools for interacting with the Google Tag Manager API, letting agents read (get, list) and modify (create, update, remove, revert) GTM resources such as tags, triggers, variables, and containers, plus separate tools for publishing container versions and deleting containers. Read-only actions are split from write actions so the server can run read-only by default, and sign-in to Google is brokered per caller.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Google Tag Manager MCP
An MCP server for Google Tag Manager, built to deploy on
foro.sh as the Google Tag Manager blueprint. The tools are
Stape's (google-tag-manager-mcp-core,
Apache-2.0), served unchanged behind foro's gate. Stape is not affiliated with foro; see NOTICE.
Read-only by default
Stape registers one tool per resource, with an action that mixes reads and writes (gtm_tag
creates, lists and deletes tags). foro allows or blocks whole tools and asks Google only for the
scopes the allowed tools need, so this server splits each one:
gtm_tagkeeps the read actions (get,list) and needs onlytagmanager.readonly.gtm_tag_edittakescreate,update,remove,revertand needstagmanager.edit.containers.Actions that need another scope get their own tool:
gtm_version_publish(tagmanager.publish),gtm_container_delete(tagmanager.delete.containers), and so on.
tools.ts is the whole table. Each scope is the narrowest Google's
discovery document accepts for the
method behind the action. A Stape tool or action not in the table is not served, and the tests fail
until it is classified, so an upstream release can't slip a write in as a read.
foro-tools.json is what foro reads to tell reads from writes and to pick the
scopes. It is generated: run npm run manifest after changing tools.ts.
Related MCP server: Google Tag Manager MCP Server
Sign-in
The server holds no OAuth of its own. foro signs each member in to Google with foro's own Google
client and keeps the refresh token; per call, the server asks foro's upstream broker for the
caller's access token under the google grant (broker.ts). It only runs inside a
foro deploy, which sets FORO_UPSTREAM_BROKER_URL and FORO_UPSTREAM_BROKER_TOKEN.
Development
npm install
npm testUpdating Stape: bump google-tag-manager-mcp-core in package.json, run npm test, classify any
new tool or action in tools.ts, then npm run manifest.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Provides read access to your GKE and Kubernetes resources.
Read and edit GA4, Search Console and Google Tag Manager from any MCP client. 29 tools.
Authenticated FieldRobin workspace tools, including scope-authorized customer and job creation.
Read spaces, collections, pages and content; search docs and manage GitBook organization spaces.
Related MCP Servers
- AlicenseBqualityBmaintenanceProduction-grade MCP server for the Google Tag Manager API v2 with read-only GA4 (Admin + Data API) tooling. 107 tools covering the full GTM surface, including server-side containers. Ships read-only: writes, publishes, and deletes are each gated behind separate opt-in flags, every mutation requires per-call confirmation, and a dry-run mode simulates changes. Includes container audits203663 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage Google Tag Manager accounts, containers, workspaces, tags, triggers, variables, and versions via the Tag Manager API v2.2Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables reading, drafting, and publishing Google Tag Manager configurations (accounts, containers, tags, triggers, variables, versions) via the Tag Manager API v2, with isolated workspaces for safe edits and explicit publish for production changes.-
- AlicenseBqualityCmaintenanceEnables LLMs to read and manage Google Tag Manager accounts, containers, workspaces, tags, triggers, variables, versions, and permissions through all 106 API v2 methods, plus task-oriented tools, with ID-based addressing and optional read-only mode.112MIT