google-data-mcp
Related Servers
Alternatives to google-data-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.209 npmApache 2.0
- 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
- AlicenseAqualityCmaintenanceEnables AI assistants to query Google Analytics 4 properties for standard, pivot, realtime, and batched reports, discover accounts, properties, and metadata, and optionally manage custom dimensions, metrics, and key events.14MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI apps to plan, build, audit, and report on Google Ads, GA4, Search Console, and Tag Manager accounts through natural language. Accounts are read-only by default, and every change is validated in a preview, applied only after confirmation, logged, and reversible.4MIT
- AlicenseNot gradedqualityDmaintenanceAutomates Google Analytics 4 and Google Tag Manager setup, management, and health monitoring with blueprints, multi-environment support, and MCP tools for AI agents.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Claude and Cursor to run read-only Google Analytics 4 queries — reports, funnels, realtime data, property and stream setup, custom dimensions, plus tracking-health checks for duplicate transactions and traffic attribution — with a one-time browser Google sign-in and no Google Cloud project required. GA4 data flows directly from the local machine to Google, and only read-only analytics access is requested.Apache 2.0
TDQS
Scored across 45 tools
Most tools have distinct resource+action pairs, but a cluster of read/backup tools overlaps heavily: gtm_export_container vs gtm_export_version vs gtm_export_workspace vs gtm_list_entities, plus gtm_list_versions and backup_list/backup_read, require careful reading to pick correctly. The descriptions do explicitly disambiguate these (e.g. 'live version overview' vs 'complete backup'), which keeps it workable, but an agent can easily select the wrong one on the first try.
Strong, predictable ga4_/gtm_ prefix scheme with verb_noun suffixes for the vast majority (gtm_create_version, ga4_list_properties, gtm_delete_entity). A handful of outliers break the pattern: backup_list and backup_read invert to noun_verb, and gtm_workspace_status, gtm_quick_preview, gtm_container_snippet, google_token_info lack a verb entirely.
45 tools is heavy, but the server genuinely spans two large products (GA4 + GTM) with reporting, admin, versioning, and backup concerns. Still, several niche tools (gtm_import_gallery_template, gtm_enable_built_in_variables, ga4_create_annotation) could plausibly be folded into the existing escape hatches, trimming the surface.
Near-complete lifecycle coverage: GTM gets accounts, containers, workspaces, entity CRUD, sync/conflict resolution, preview, version create/publish/rollback, and templates; GA4 gets core/realtime/funnel reporting, metadata, compatibility checks, admin objects, redaction, annotations, and change history. The gtm_request and ga4_admin_request escape hatches cover anything left out, so there are no real dead ends.