Connectors
Updated

Google Tag Manager MCP connector

The Google Tag Manager connector lets AI agents audit and edit GTM containers through InsightfulPipe's hosted MCP server at https://google-tag-manager.insightfulmcp.com/. You connect it with a Google sign-in, and every change an agent makes stays in a GTM workspace until someone publishes it in Google Tag Manager.

Google Tag Manager MCP server reference

Endpoint
https://google-tag-manager.insightfulmcp.com/
Server name
google-tag-manager-mcp
Actions
61 (38 read, 23 write). Workspace owners, admins and operators choose which actions each connected account exposes, and destructive actions are off by default.

Add it from a terminal, then click Authorize access in the browser window that opens:

claude mcp add --transport http google-tag-manager-mcp https://google-tag-manager.insightfulmcp.com/
gemini mcp add --transport http google-tag-manager-mcp https://google-tag-manager.insightfulmcp.com/
codex mcp add google-tag-manager-mcp --url https://google-tag-manager.insightfulmcp.com/

What agents can do

The server has 61 actions (38 read, 23 write). See the full action list.

  • Accounts and containers: get_accounts, get_containers, lookup_container (find a container by its public GTM ID) and get_container_snippet (the install snippet).
  • Workspaces: get_workspaces, get_workspace_status (pending changes and merge conflicts) and quick_preview_workspace.
  • Tags, triggers and variables: get_tags, get_triggers, get_variables, get_built_in_variables and get_folders, plus get_folder_entities.
  • Versions: get_live_version, get_version, get_version_headers and get_latest_version_header.
  • Templates, server-side and more: get_templates, get_gtag_configs, get_environments, get_destinations, get_clients, get_transformations and get_zones.
  • Build in a workspace: create_workspace, create_tag, update_tag, create_trigger, update_trigger, create_variable, update_variable, create_folder, update_folder, move_entities_to_folder and enable_built_in_variable.
  • Undo and merge: revert_tag, revert_trigger, revert_variable, revert_folder, sync_workspace and resolve_conflict.
  • Delete: delete_tag, delete_trigger, delete_variable, delete_folder, delete_workspace and disable_built_in_variable, all off by default.

Before you connect

  • A Google login with access to at least one Google Tag Manager account.
  • An InsightfulPipe workspace with a brand for the account. Owners, admins and operators can add connections.
  • No Google Cloud project is needed.

Connect Google Tag Manager

  1. In the InsightfulPipe app, open Connectors, choose Google Tag Manager and click Connect.
  2. Under Permissions, choose Read Only or Read + Write.
  3. Sign in with Google and approve access.
  4. Choose the GTM accounts to connect in the account picker, then click Connect. Each selected account becomes its own connection.

Add the MCP server to your AI client

Server URL: https://google-tag-manager.insightfulmcp.com/ and server name: google-tag-manager-mcp.

  • Claude: open Claude Connectors Settings, scroll to the bottom and click Add custom connector, paste the URL, click Add, then click Connect.
  • ChatGPT: in ChatGPT Security Settings turn on Developer mode, click Create on the Connectors page, paste the URL, click Create, then click Connect. Turn the connector on in each new chat with + → More.
  • Claude Code: run claude mcp add --transport http google-tag-manager-mcp https://google-tag-manager.insightfulmcp.com/, then type /mcp, select google-tag-manager-mcp and click Authenticate.
  • Cursor: in the app, open MCP Servers, choose Google Tag Manager and click Install Google Tag Manager MCP, click Open Cursor then Install, then click Connect and Open.
  • Gemini CLI: run gemini mcp add --transport http google-tag-manager-mcp https://google-tag-manager.insightfulmcp.com/, then /mcp auth google-tag-manager-mcp.
  • Codex CLI: run codex mcp add google-tag-manager-mcp --url https://google-tag-manager.insightfulmcp.com/; authorization starts automatically.

Each client opens a browser window where you log in to InsightfulPipe and click Authorize access. Step-by-step guides: Claude, ChatGPT, Claude Code, Cursor, Gemini CLI and Codex CLI. To reach every connected platform through one server, use the unified server.

Permissions and safety

  • Read Only connections request Google's read-only Tag Manager permission and can't run write actions. Read + Write also requests permission to edit containers and container versions.
  • Nothing goes live on its own. The server has no action that creates or publishes a container version, so a person reviews, previews and publishes the workspace in Google Tag Manager.
  • delete_tag, delete_trigger, delete_variable, delete_folder, delete_workspace and disable_built_in_variable are destructive, so they stay off until an owner, admin or operator enables them in Configure actions for this account.
  • update_tag, update_trigger and update_variable overwrite the workspace copy and are regular writes, and revert_* discards uncommitted workspace changes. Turn them off where agents should only audit.
  • Write actions need the Owner, Administrator or Operator role. Members with the User role only get the enabled read actions on accounts granted to them.

Limits

  • Creating versions and publishing happen in Google Tag Manager.
  • Delete workspaces in Google Tag Manager. InsightfulPipe doesn't request the Tag Manager permission Google requires for deleting workspaces, so delete_workspace is expected to be refused by Google even when enabled.
  • Custom templates, Google tag configurations, environments, destinations, server-side clients, transformations and zones can be read but not created or edited.
  • Tag parameters must match what the GTM API expects for each tag type, so check new tags in Preview mode before publishing.
  • The action list agents see leaves out single-item lookups such as get_tag and get_trigger to stay short. Agents can still call them by name.

Example prompts

  • "List all tags in the Default Workspace of GTM-ABC1234 with their firing triggers."
  • "Find paused tags and tags that have no firing trigger."
  • "In a new workspace, create a GA4 event tag for form_submit that fires on form submissions."
  • "What changed between the live version and the previous version?"

Troubleshooting

  • "No Google Tag Manager accounts found": sign in with a Google account that has access to at least one GTM account, or ask a GTM admin to add you.
  • "This action is disabled for this connected account. An owner or admin must enable it for the account.": an owner, administrator or operator can turn the action on in Configure actions for this account.
  • "This account is connected read-only, so this action cannot be enabled for it. An owner or admin must reconnect it with Read & Write permissions.": reconnect the account and choose Read + Write.
  • Changes don't appear on the site: the agent only edits the workspace. Preview and publish it in Google Tag Manager.
  • A workspace can't be deleted: delete it in Google Tag Manager.

FAQ

Can an agent publish changes to my live site?

No. All changes stay in a GTM workspace, and the server cannot create or publish container versions. Publishing is always done by a person in Google Tag Manager.

Can I connect more than one GTM account?

Yes. When you sign in with Google, you choose which GTM accounts to connect, and each one becomes its own connection. Agencies can connect one account per client and review containers across them in one conversation.

Does it work with server-side containers?

It can read server-side clients, transformations and zones, and work with tags, triggers and variables in those containers, but it can't create or edit clients, transformations or zones.

Related

Need help?

If you need help connecting a source or setting up an AI workflow, the team can help you get from first sync to production faster.

Read the blogStart a trial