Samarth GTM MCP Server
OfficialRelated Servers
Alternatives to Samarth GTM MCP Server
No user-submitted related servers found.
Related Servers
- 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.-
- 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.2573 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Google Tag Manager API v2, enabling programmatic management of accounts, containers, workspaces, tags, triggers, variables, and version workflows.20 npm15MIT
- AlicenseBqualityAmaintenanceMCP 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
- AlicenseAqualityAmaintenanceSelf-hosted Google Analytics 4 MCP server with 27 read-only tools for the Google Analytics Data and Admin APIs. Maintained source relocated to get-mcp-ads/google-analytics-mcp-server; npm package remains @getmcpads/google-analytics-mcp-server.2765 npmApache 2.0
- AlicenseAqualityBmaintenanceMCP server for Google Tag Manager and GA4, enabling tag management, consent auditing, workspace versioning, and analytics reporting through natural language.1137 npm2MIT
TDQS
Scored across 181 tools
Most tools follow a clear resource/action pattern and target distinct GTM or GA4 resources, so the intended purpose is usually obvious. However, convenience tools like create_gtm_tracking_tag and create_gtm_variable_typed overlap with tags_create and variables_create, creating some selection ambiguity.
GTM tools mostly use resource-first naming (tags_list, tags_create), and GA4 reads use a similar ga4_<resource>_list/get pattern. But GA4 writes flip to action-first naming (ga4_create_property, ga4_update_custom_dimension), and a few GTM tools are verb-first (create_gtm_tracking_tag) or inconsistently use workspace singular/plural, producing two readable but inconsistent conventions.
181 tools is far beyond the 25+ threshold and creates a very large selection surface for an agent. The breadth may be justified by combining the GTM and GA4 Admin APIs, but it would be better split into smaller, more focused MCP servers or consolidated with more parameterized tools.
Core GTM workflows (tags, triggers, variables, versions, workspaces) have strong lifecycle coverage, and GA4 has broad CRUD support. However, many GA4 resources have create/update/delete without corresponding list/get operations (e.g. audiences, measurement protocol secrets, event create rules, access bindings), so agents cannot easily discover existing entities before managing them.