All servers / Search / Google Search Console MCP server
Google Search Console MCP server
Google Search Console MCP server — query search analytics, inspect URLs, manage sitemaps more via natural language
Tested by ConnectATDScore 94 out of 100. Tested 2026-11-18 on package version 0.4.1. Package: mcp-gsc · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 16 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (24.1 seconds including download)
- Tools offered: 21
- Last published: 2026-10-22
- Weekly downloads (npm): 11,403
- License: MIT · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
list_propertiesno parametersList all Google Search Console properties you have access to, with permission levels and verification status.
get_property_details1 of 1 parameter describedGet verification info, ownership, and permissions for a specific Google Search Console property.
search_analytics10 of 10 parameters describedQuery Google Search Console search performance data (clicks, impressions, CTR, position) with filtering and grouping. DIMENSIONS: query, page, country, device, date, searchAppearance, hour - "hour" requires data_state="hourly_all" and is limited to the last 10 days - "searchAppearance" CANNOT be combined with "query" or "page" (API restriction) TYPE: web (default), image, video, news, discover, googleNews - "discover" = Google Discover feed. "googleNews" = Google News tab (distinct from "news") DATA STATE: Controls data freshness. - "all" (default) includes recent incomplete data matching the GSC dashboard - "final" returns only confirmed data with a 2-3 day lag, useful for stable reporting - "hourly_all" enables hourly granularity but data may be incomplete for the current day BRAND FILTER: Set to "brand_only" or "non_brand_only" to auto-filter queries by your domain name. Country codes use ISO 3166-1 alpha-3 format (e.g., 'usa', 'gbr', 'deu') — NOT alpha-2.
list_sitemaps2 of 2 parameters describedList all sitemaps for a property with status, type, indexed URL counts, errors/warnings.
get_sitemap2 of 2 parameters describedGet detailed info for a specific sitemap including content breakdown by type (web, image, video, etc.).
inspect_url2 of 2 parameters describedInspect a URL's indexing status, crawl info, rich results, mobile usability, and canonical URLs. Counts against the daily 2,000 and per-minute 600 URL Inspection limits.
batch_inspect_urls2 of 2 parameters describedInspect up to 10 URLs simultaneously. Returns categorized results (indexed, not indexed, issues). Each URL counts against the daily 2,000 and per-minute 600 URL Inspection limits.
export_csv6 of 7 parameters describedExport search analytics data to a CSV file on the machine running this server. Pages through results internally (25K rows per API call, up to 40 calls) to write the full dataset, bypassing the tool response row cap. Note: Google itself caps how many rows it exposes per day and search type (sorted by clicks), so very large sites may not get the complete long tail. Use dimension_filters to split the export into smaller slices if needed.
performance_overview4 of 4 parameters describedAggregate metrics (total clicks, impressions, avg CTR, avg position) plus a daily trend breakdown for a property. Single API call.
compare_periods6 of 6 parameters describedCompare two date ranges with delta calculations (absolute change + percentage change) for each dimension value. Makes 2 API calls.
top_movers6 of 6 parameters describedBiggest gains and drops in clicks/impressions/position between two periods. Period A = start_date to end_date. Period B = the comparison_days before start_date.
device_country_breakdown4 of 4 parameters describedPerformance breakdown by device type and/or country.
quick_wins7 of 7 parameters describedFind high-impression, low-CTR queries in striking distance (position 4-20). These are opportunities to improve rankings and CTR with small content or SEO tweaks.
cannibalization5 of 5 parameters describedDetect keyword cannibalization — multiple pages ranking for the same query. Uses query + page dimensions to find overlap.
opportunity_finder4 of 4 parameters describedFind queries with improving impressions but low clicks, new emerging queries, and declining performers. Makes 2 API calls to compare periods.
position_tracking6 of 6 parameters describedTrack position changes for specific queries or pages over time. Uses date dimension with query/page filters. Returns daily or weekly averages.
ctr_anomalies4 of 4 parameters describedDetect queries/pages with abnormally low or high CTR relative to their position. Uses expected CTR curves per position bucket and flags deviations.
content_decay6 of 6 parameters describedDetect pages/queries where impressions have dropped significantly compared to their historical peak within the 16-month API window.
weekly_seo_report4 of 4 parameters describedAll-in-one SEO report: runs performance overview + quick wins + top movers + indexing issues summary. Returns a combined markdown report.
indexing_coverage2 of 2 parameters describedBatch-inspect user-provided URLs and categorize by indexing status: indexed, not indexed, canonical mismatch, robots blocked, fetch error, other. Respects URL Inspection rate limits.
sitemap_health1 of 1 parameter describedAnalyze all sitemaps: error/warning patterns, submission freshness (days since last submitted), indexed vs submitted ratio per sitemap.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.