gsc-coverage
Related Servers
Alternatives to gsc-coverage
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables users to query search performance, indexing, sitemaps and properties in plain language from any MCP client, returning worked-out analysis such as cannibalization, striking-distance keywords and decaying pages, with multilingual query variants merged so totals are correct. It also syncs data to a local store for history beyond Google's 16-month limit, including a 24-hour view, hourly data and timezone-adjusted days.3739 PyPI2MIT
- AlicenseBqualityCmaintenanceEnables AI assistants and MCP clients to analyze Google Search Console SEO data in plain English, including search analytics, URL inspection, sitemaps, indexing requests, hourly performance, CSV export, and computed SEO insights.38MIT
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive access to Google Search Console data with enhanced analytics capabilities, supporting up to 25,000 rows of performance data, advanced filtering with regex patterns, and automatic detection of SEO optimization opportunities.5,260 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to fetch Google Search Console search analytics reports (clicks, impressions, CTR, position) over MCP, with support for custom date ranges, dimensions, filters, comparisons, and exports.MIT
- -licenseNot gradedqualityNot gradedmaintenanceProvides comprehensive access to Google Search Console data with enhanced analytics capabilities, supporting up to 25,000 rows of performance data, advanced filtering with regex patterns, and automatic quick wins detection for SEO optimization opportunities.2-
- AlicenseNot gradedqualityBmaintenanceExposes Google Search Console's API as MCP tools for SEO analytics, including up to 25,000-row search analytics, regex filters, quick-win and cannibalization detection, period comparisons, sitemap/site management, and batch URL inspection, accessible over stdio, HTTP/SSE with bearer auth, or Cloudflare Workers.5,260 npmMIT
TDQS
Scored across 2 tools
The two tools target completely different resources: list_sites enumerates accessible properties, while search_analytics pulls performance rows with coverage metadata. There is no plausible way to confuse one for the other, and the descriptions make the boundary explicit.
Both names follow the same snake_case verb_noun convention (list_sites, search_analytics), with clear resource nouns. The pattern is predictable and would extend naturally if more tools were added.
Two tools is thin for a Search Console surface, even a narrowly scoped one; a single discovery tool plus a single query tool leaves little room for workflow support. It is defensible for a read-only, coverage-focused server, but sits at the borderline of the 1-2 tool range.
The core read path is covered end to end: discover properties, then pull paged performance data with totals and truncation reporting so agents can reason about coverage. Minor gaps exist around adjacent Search Console operations (e.g. sitemaps, URL inspection, or dimension/metric discovery), but nothing that blocks the stated purpose.