jptb-google-tools
Related Servers
Alternatives to jptb-google-tools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage Google Tag Manager, Google Search Console, and Google Analytics (GA4) through unified access to tags, search performance data, URL inspection, sitemaps, and analytics reporting.5 npmISC
- AlicenseAqualityAmaintenanceEnables AI agents to read and write Google Analytics 4, Search Console, and Tag Manager data through MCP tools, with write operations gated behind an explicit flag for safety.207 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables AI assistants to access and manage Google Drive, Sheets, Docs, Calendar, and Gmail through OAuth2-authenticated MCP tools.271MIT
- AlicenseBqualityBmaintenanceProvides AI agents with hands-on control of Google SEO and analytics tools including Search Console, GA4, Tag Manager, Indexing API, and PageSpeed Insights, with self-configuring OAuth2.3314 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Google Analytics 4 data, providing tools for historical reporting, real-time activity monitoring, and property management. It supports secure service account authentication to access metrics like traffic summaries, user acquisition, and custom dimensions.MIT
- FlicenseAqualityAmaintenanceEnables AI agents to manage multiple Google accounts with persistent sessions and anti-detect browser fingerprints, supporting sign-in, account switching, Gmail access, and interaction with any Google SSO website.42-
TDQS
Scored across 24 tools
Each tool is scoped by a clear product prefix (gtm_/ga4_) and a specific resource/action, so tags, triggers, variables, versions, and GA4 reporting tools are all easily distinguishable. The two resolve tools are also cleanly separated by domain. There is no meaningful overlap between tools.
Tools overwhelmingly follow a product_verb_noun pattern in snake_case, such as gtm_list_tags, gtm_update_trigger, and ga4_run_report. The only minor deviation is gtm_resolve and ga4_resolve, which omit an explicit noun object, though they are still consistent with each other and easy to understand.
24 tools is above the typical 3-15 sweet spot and feels slightly heavy, but the count is justified by covering two distinct Google products with multiple subresources. Each tool has a specific purpose, so the set is not bloated or redundant.
The GTM toolset covers the core tag/trigger/variable workflow through create, update, version, and publish, and the GA4 toolset covers property lookup and reporting. Minor gaps exist, such as no delete operations for GTM resources and no individual get for tags/triggers/variables, but these can generally be worked around with list operations.