Google Tag Manager MCP
Related Servers
Alternatives to Google Tag Manager MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for Google Tag Manager API, enabling users to manage containers, tags, and triggers through natural language using Google Application Default Credentials.1878 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server for Google Tag Manager API v2, enabling programmatic management of accounts, containers, workspaces, tags, triggers, variables, and version workflows.13 npm14MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP Server that provides a conversational interface to Google Tag Manager API, allowing users to manage tags, triggers, variables, and containers through natural language.-
- AlicenseAqualityBmaintenanceAn MCP server for the Google Tag Manager API v2 that enables AI assistants to query GTM accounts, containers, tags, triggers, variables, and unpublished changes.242Apache 2.0
- FlicenseNot gradedqualityBmaintenanceA remote MCP server for Google Tag Manager that enables AI assistants to manage GTM accounts, containers, tags, triggers, variables, and more via OAuth or service account authentication.1-
- FlicenseNot gradedqualityBmaintenanceMCP server for Google Tag Manager, offering tools to manage accounts, containers, workspaces, tags, triggers, and versions, with explicit confirmation for production-affecting actions.-
TDQS
Scored across 19 tools
Most tools target distinct resources or actions clearly. The generic get_resource and create_entity/update_entity/delete_entity are broad but their descriptions clarify which resource types they apply to. publish_version with multiple actions (publish, get, live) overlaps slightly with get_resource, but this is manageable.
The dominant pattern is verb_noun (list_accounts, get_container, create_workspace, update_entity, delete_entity). Deviations include manage_built_in_variables, publish_version, and raw_request, which break the clean pattern but remain understandable. The generic entity suffix is less specific than named resources but consistent across create/update/delete.
With 19 tools covering accounts, containers, workspaces, entities, versions, and a raw escape hatch, the count is higher than average but justified by GTM's broad API surface. The set feels comprehensive without being bloated, and the raw_request tool reduces the need for many specialized tools.
Core workflows are covered: accounts, containers, workspaces, entity CRUD, version creation, and publishing. Some operations lack dedicated tools (update/delete container, workspace update/delete, version listing), but raw_request fills these gaps. The main tag management lifecycle is fully supported, with minor workarounds needed for edge cases.