ga4-seo-mcp
Related Servers
Alternatives to ga4-seo-mcp
No user-submitted related servers found.
Related Servers
- 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.209 npmApache 2.0
- 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 gradedqualityBmaintenanceLets AI assistants analyze search performance, inspect URLs and indexing issues, and manage sitemaps through read/write actions, with destructive operations disabled by default.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.7 npmISC
- AlicenseBqualityCmaintenanceProvides 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.3311 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables querying Google Analytics 4 traffic, engagement, and conversions, as well as Google Search Console performance, index status, and sitemap management.2 npmMIT
TDQS
Scored across 24 tools
Most tools have distinct resource+action targets, and the descriptions clearly separate similar pairs (psi_audit vs psi_field_data_only, web_vitals_summary vs psi_field_data_only). However, top_pages, events_summary, traffic_sources and conversions_summary are all essentially preset versions of run_report, creating mild overlap an agent must reason about.
Names use consistent snake_case verb_noun within each domain (list_properties, get_property, run_report; sc_list_sites, sc_top_queries; psi_audit). The sc_/psi_ prefixes are meaningful namespacing, though GA4 tools carry no prefix, leaving a minor stylistic inconsistency across domains.
24 tools is on the heavy side for the stated scope and exceeds the comfortable 3-15 range. Several reporting tools (top_pages, events_summary, traffic_sources, conversions_summary) are convenience wrappers around run_report, so the surface is somewhat inflated.
Reporting, GA4 admin reads, Search Console analytics and PageSpeed are well covered, and bootstrap_site_measurement handles provisioning. Gaps exist: no GA4 config write/update tools and no sc_verify_site_dns/sc_submit_sitemap tools despite bootstrap referencing them as follow-up steps.