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.1869 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.20 npm15MIT
- 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.-
- AlicenseAqualityFmaintenanceAn MCP server for the Google Tag Manager API v2 that enables AI assistants to query GTM accounts, containers, tags, triggers, variables, and unpublished changes.241Apache 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 25 tools
Most tools have clearly distinct purposes, with specific list/get/create/update/delete operations for each resource type. The generic get_resource and raw_request tools are well-described as fallbacks, but they could cause minor confusion with the dedicated getters. Auth-related tools are distinct and clearly separated.
The majority of tools follow a consistent verb_noun pattern (list_triggers, create_container, update_entity). A few auth-related tools (auth_status, setup_instructions, set_client, start_login, finish_login, logout) and raw_request deviate from this pattern, but they are clearly named and don't disrupt the overall consistency.
With 25 tools, the server is on the heavier side but appropriately scoped for the Google Tag Manager API, which has many resource types and operations. Each tool covers a meaningful part of the domain, and the count is justified by the complexity of GTM.
The tool set covers the core GTM lifecycle: account/container/workspace management, CRUD for tags/triggers/variables, built-in variable toggles, and version creation/publishing. The raw_request escape hatch fills gaps for less common resources (environments, folders, templates), making the surface quite complete, though a few dedicated tools could be added for those.