Samarth GTM MCP Server
OfficialRelated Servers
Alternatives to Samarth GTM MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables auditing Google Tag Manager containers, checking GA4 ecommerce event coverage, previewing and applying workspace edits as dry-run diffs, and publishing versions with explicit confirmation. Runs locally over stdio with your own Google OAuth account, enforcing read-only or read/write/publish profiles and client-side rate limiting.34MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for Google Tag Manager, offering tools to manage accounts, containers, workspaces, tags, triggers, and versions, with explicit confirmation for production-affecting actions.-
- AlicenseAqualityBmaintenanceMCP 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.25408 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Google Tag Manager API v2, enabling programmatic management of accounts, containers, workspaces, tags, triggers, variables, and version workflows.46 npm15MIT
- AlicenseBqualityCmaintenanceMCP server for Google Analytics 4 and Google Tag Manager with read and write access, providing 40 tools to manage GA4 reports, audiences, and GTM tags, triggers, and variables via natural language.40MIT
- 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 203 tools
Most CRUD tools are cleanly separated by resource (tags_*, triggers_*, ga4_*), but the write surface has real overlap: tags_create competes with create_gtm_tracking_tag, create_server_tag, the dozen create_*_capi_server_tag tools, and templates_import_from_gallery, all of which produce tags. The descriptions explicitly try to steer the agent ("use this instead of tags_create"), which mitigates but doesn't remove the boundary problem, and 203 near-identical ga4_create_/update_/delete_ triples increase misfire risk at the margins.
The dominant pattern is resource_verb (tags_create, folders_move_entities, ga4_update_property), but the server mixes in verb_noun forms (create_gtm_tracking_tag, create_meta_capi_server_tag, audit_container, export_container, plan_server_migration_from_web) and inconsistent resource grouping (workspace_sync / workspace_get_status alongside workspaces_list / workspaces_create). Readable throughout, but the convention shifts depending on which family a tool belongs to.
203 tools is roughly four times the rubric's own ceiling, and the resulting context cost makes tool selection the dominant failure mode for an agent. Nearly every tool does map to a distinct GTM/GA4 API method rather than duplicating another, so it is an over-broad surface rather than a padded one — but the count is still inappropriate for practical use without progressive disclosure or sub-server splitting.
Coverage is genuinely deep: full CRUD for containers, workspaces, tags, triggers, variables, folders, versions, environments, permissions, clients, transformations, zones, templates and gtag configs, plus GA4 Admin CRUD, Data API reporting and per-platform server-side tag builders. The notable gap is read/list counterparts for several GA4 resources that have create/update/delete (audiences, channel groups, calculated metrics, event-create rules, access bindings) — an agent can mutate these but not enumerate them.