google-search-console-mcp-server
Related Servers
Alternatives to google-search-console-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides read-only access to Google Search Console data, including search analytics, sitemap status, and URL inspection, for MCP clients like Claude.6 npmMIT
- AlicenseAqualityAmaintenanceEnables MCP clients such as Claude to read Google Search Console data, including search analytics, sitemaps, and URL inspection, so users can answer SEO questions with real numbers while remaining read-only.42MIT
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server for Google Search Console data, enabling search analytics, URL inspection, indexing diagnostics, and sitemap management through MCP clients.7 npmMIT
- AlicenseAqualityBmaintenanceEnables MCP clients to retrieve Search Console search analytics, find multilingual question-shaped queries and SEO opportunities, inspect URLs, and view or manage sitemaps with server-side date resolution and comparisons.6MIT
- AlicenseAqualityAmaintenanceEnables local, read-only access to Google Search Console data, allowing users to query site performance, identify ranking opportunities, inspect URL indexing, and review sitemap status through MCP clients.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to list accessible Search Console properties and query search-analytics data—clicks, impressions, CTR, and position—over date ranges grouped by chosen dimensions, authenticating read-only as the user's own Google account.67 npmMIT
TDQS
Scored across 20 tools
Most tools have distinguishable purposes, but there is notable overlap in the monitoring/health cluster (get_sitemap_health, monitor_indexation_freshness, get_data_freshness, track_sitemap_deltas) and the URL-inspection cluster (inspect_url, bulk_inspect_urls, indexation_watchlist, plan_large_site_sampling). The analytics-derived tools (compare_search_types, find_losses_gains, cluster_queries, detect_cannibalization) also blur together since they all wrap Search Analytics. Descriptions help, but boundaries require careful reading.
Every tool uses a uniform gsc_ prefix with snake_case and a predictable verb_noun pattern (list_sites, get_site, inspect_url, list_sitemaps, query_search_analytics). No convention mixing or vague one-word names.
20 tools is on the heavy side for a read-only Search Console surface. Several tools are thin analytical wrappers or overlapping monitors that could be consolidated, suggesting feature sprawl rather than a tightly scoped set.
Coverage is broad for a read-only server: sites, analytics, URL inspection, sitemaps, and multiple analytical views. Write operations (sitemap submission, site add/remove) are absent, but these are outside the stated read-only scope, leaving only minor gaps.