google-analytics-mcp-server
Related Servers
Alternatives to google-analytics-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables querying Google Analytics 4 data through MCP tools for running reports, listing properties, getting real-time metrics, and exploring metadata.1 npmMIT
- AlicenseAqualityDmaintenanceEnables querying Google Analytics 4 properties using natural language through MCP clients. Supports customizable reports with any dimensions and metrics, listing properties, and real-time data.4MIT
- AlicenseBqualityBmaintenanceEnables read-only Google Analytics 4 reporting through MCP, including daily summaries, top pages, acquisition, events, realtime activity, metadata, and custom reports with CSV/JSON output.8MIT
- AlicenseAqualityAmaintenanceEnables read-only access to Google Analytics 4 data through seventeen tools covering reports, realtime data, funnels, pivots, metadata, and admin lists. It runs locally with service account credentials and lets users query properties via standard MCP clients.1751 PyPIMIT
- FlicenseNot gradedqualityCmaintenanceRead-only access to Google Analytics 4 reporting data, including traffic overview, top pages, traffic sources, and conversion events, supporting custom report queries via MCP.-
- FlicenseNot gradedqualityCmaintenanceEnables querying Google Analytics 4 data through natural language, including running reports, comparing periods, and exploring realtime metrics across multi-tenant properties with OAuth-based authentication.-
TDQS
Scored across 27 tools
Most tools name a distinct GA4 resource and action, so core reporting/metadata/admin tools are easy to separate. However, several overlapping clusters remain—validate_query vs check_compatibility, the two funnel reporters, and the audience-diagnostics/export trio—which can cause misselection despite helpful descriptions.
All 27 tools consistently use a ga4_ prefix with snake_case verb_noun names like list_properties, run_pivot_report, and get_audience_export_diagnostics. The prefix immediately identifies the server domain and the verb establishes intent, so names are highly predictable.
27 tools is on the heavy side; the long line of one-off diagnostics and redundant funnel/report variants makes the set feel larger than necessary. Still, the GA4 surface covered is broad and most tools target a distinct endpoint, so the count is more borderline than clearly overblown.
For an intentionally read-only GA4 server, the core lifecycle is covered: discover accounts/properties, run core/realtime/pivot/funnel/batch reports, inspect metadata/custom definitions/events, and diagnose integrations. Minor gaps such as no direct data-stream getter and no account-level aggregation keep it from a perfect 5.