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.4 npmMIT
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server for Google Search Console data, enabling search analytics, URL inspection, indexing diagnostics, and sitemap management through MCP clients.11 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
- AlicenseAqualityAmaintenanceRead-only MCP server for Google Search Console: performance queries, URL inspection, indexing checks, sitemaps, and one-call HTML SEO audit reports.17229 PyPI8MIT

io.scalably/gsc-mcpofficial
AlicenseAqualityAmaintenanceEnables read-only access to Google Search Console data, including properties, Search Analytics with filters and auto-pagination, sitemaps, and URL inspection with batch support and throttling.547 PyPIMIT
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.