The Google Tag Manager MCP that builds and publishes

Google Tag Manager MCP connects GTM to Claude, ChatGPT, Cursor, and other MCP-compatible AI clients. The assistant can inspect your containers and workspaces, create or update GTM entities, preview changes, and prepare version publishing through Markifact.

No. It provides full read and write management. The current integration exposes 97 GTM operations: 37 read operations and 60 approval-gated writes covering the complete container lifecycle.

Accounts, containers, workspaces, tags, triggers, user-defined and built-in variables, versions, server-side clients, folders, templates, transformations, zones, Google tag configs, environments, and linked destinations.

Yes. The AI can inspect existing entities, prepare the trigger and variables a tag needs, create the complete stack in a workspace, and keep everything unpublished until you approve the writes.

Yes. You can manage server containers, clients that receive and route requests, transformations that modify event data before tags run, templates, and the other entities used in server-side GTM.

Yes. It can inspect workspace status, quick-preview without creating a real version, report compiler errors, sync against the latest container, resolve conflicts, create a named version, and prepare that version for publishing.

Yes. Publishing changes the live configuration on every site or app using the container, so gtm_publish_version and every other GTM write stop for explicit approval in Markifact.

Yes. Revert operations can discard workspace changes for tags, triggers, variables, clients, folders, templates, transformations, zones, and built-ins. Deleted versions can be restored, and you can set which version new workspaces use.

Yes. List, create, update, delete, and reauthorize user environments such as Staging, inspect their authorization codes, and list or link Google tag destinations such as GA4 measurement IDs.

Yes. Markifact exposes both operations, but they are high-impact writes. Combining containers retires the source and cannot be undone, while moving a public GTM ID creates a new container. Both require approval.

No custom developer setup is required. Connect your Google account with OAuth and Markifact handles the hosted MCP server and Tag Manager API authentication.

Yes. List the GTM accounts and containers available to the connected Google user, then switch account, container, workspace, environment, or version context inside the conversation.

Markifact separates inspection from mutation. Read tools can audit the account immediately, while every create, update, delete, sync, conflict resolution, version, environment, destination, merge, and publish operation requires human approval.