Google Tag Manager MCP Server
Related Servers
Alternatives to Google Tag Manager MCP Server
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to manage Google Tag Manager accounts and containers through the Tag Manager API v2, covering account/container discovery, workspace creation and syncing, CRUD on tags, triggers, variables, and folders, built-in variable control, version snapshots, and guarded publishing. It authenticates with a user's own Google identity (or a service-account fallback), honors API quota limits, and writes a redacted SQLite debug log of every tool call and API request.1MIT
- AlicenseBqualityDmaintenanceEnables comprehensive management of Google Tag Manager accounts, containers, workspaces, tags, triggers, and variables through OAuth2 authentication, allowing users to create, update, and publish GTM configurations via natural language.2624 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables interaction with Google Tag Manager through its API with built-in Google OAuth authentication. Allows managing GTM containers, tags, triggers, and variables through natural language.335 npm241Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI assistants to read and manage Google Tag Manager containers, tags, triggers, variables, and other GTM resources through the GTM API v2, with all processing running locally using the user's own Google credentials.24 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to audit, automate, and manage Google Tag Manager Web and Server-Side containers via the official API, including read-only inspection, draft workspace edits, version snapshots, and guarded publishing. It runs over an isolated STDIO transport with OAuth 2.0 credentials and requires explicit confirmation before pushing changes live.MIT
TDQS
Scored across 112 tools
The consistent list/get/create/update/delete/revert pattern makes most tools clearly distinct by entity. However, version-related tools (get_version, get_live_version, get_latest_version_header, set_latest_version) and publish-related tools (publish_version, publish_workspace, create_version) could be confused at a glance, though their descriptions disambiguate them well.
Tool names follow a strict verb_noun convention throughout, with consistent CRUD verbs (list/get/create/update/delete/revert) applied per entity. Exceptions like lookup_container, quick_preview_workspace, and summarize_container are also verb-first and clear, so the pattern remains predictable.
112 tools is an extreme count, far beyond the 50+ threshold for a score of 1. While the Google Tag Manager API is broad, exposing full CRUD for a dozen entity types plus many convenience helpers results in an overwhelming surface that would be difficult for an agent to navigate efficiently.
The surface covers the full lifecycle across accounts, permissions, containers, environments, versions, workspaces, and every workspace entity type (tags, triggers, variables, folders, templates, clients, transformations, zones, gtag configs). Convenience tools for searching, summarizing, and bulk operations close most practical gaps.