enhanced_search_analytics is the reason to install this over using the interface: a single call wide enough to ask cross-sectional questions rather than page-by-page ones, with regex filters doing the segmenting. detect_quick_wins encodes the usual heuristic — high impressions, low CTR, positions inside a band you choose — and attaches conversionRate and estimatedClickValue so the result is ordered by value. Everything is bounded by what the service account has been granted in Search Console, which is a permissions question to settle before the first call rather than after.
A server over the Google Search Console API — search analytics, URL inspection and sitemap management — for the properties one service account can see.
- search_analytics with the API's own controls: dimensions, date range, search type and aggregation, plus query, page, country and device filters
- enhanced_search_analytics for the larger pull — up to 25,000 rows, regex filtering, and quick-wins detection switched on inline
- detect_quick_wins as a standalone scan with thresholds you set: an impressions floor, a CTR ceiling and a position band
- Value attached to the scan through conversionRate and estimatedClickValue, so the output ranks by what the opportunity is worth rather than by position alone
- URL-level index status from index_inspect, including whether a page can be indexed and in which language context
- Sitemaps listed, fetched by feedpath and submitted for a property
GOOGLE_APPLICATION_CREDENTIALS pointing at a Google service account credentials file, and that service account granted access to the Search Console properties you intend to read — list_sites returns what it can reach. submit_sitemap is the only tool that changes anything on Google's side; the rest read.
One command plus a key — npm install mcp-server-gsc, then supply credentials