gtm-mcp-server
Related Servers
Alternatives to gtm-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables reading, drafting, and publishing Google Tag Manager configurations (accounts, containers, tags, triggers, variables, versions) via the Tag Manager API v2, with isolated workspaces for safe edits and explicit publish for production changes.-
- AlicenseNot gradedqualityCmaintenanceEnables full Google Tag Manager management via the GTM API v2, including tags, triggers, variables, and version publishing, with workspace-based change tracking.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Google Tag Manager API v2, enabling programmatic management of accounts, containers, workspaces, tags, triggers, variables, and version workflows.18 npm15MIT
- AlicenseAqualityAmaintenanceMCP server for the Google Tag Manager API v2, enabling natural-language management of containers, workspaces, tags, triggers, variables, and publishing. It handles OAuth authentication and built-in rate limiting for the strict GTM API quota.2567 npm1MIT
- 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.-
- 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.2620 npmMIT
TDQS
Scored across 25 tools
Each tool targets a distinct resource (account, container, workspace, tag, trigger, variable) and action (list, get, create, update, delete, revert, status, sync, preview). The workspace operations are clearly differentiated by their descriptions, so misselection is unlikely.
Tool names follow a consistent gtm_<verb>_<resource> snake_case pattern for the most part, but gtm_workspace_status breaks the verb-first convention, and gtm_quick_preview_workspace uses a compound verb. Minor deviations, still readable.
25 tools is at the upper bound of reasonable for this domain. The full CRUD+revert for three entity types plus workspace management accounts for the count, but it feels heavy rather than tightly scoped.
The set covers full lifecycle for tags, triggers, and variables, and workspace drafting operations. However, there is no publish tool (explicitly avoided in descriptions) and no create/update/delete for containers or accounts, leaving a notable gap in the overall GTM lifecycle.