Google Search Console
Google Search Console: SEO audits, performance queries, URL inspection, indexing checks.
Connector by acamolese · GitHub account verified by the MCP Registry
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/acamolese-google-search-console-mcp
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.
- Tools
- 8 read · 0 write · 1 delete · 8 not yet classified
- Secrets
- 2 (API keys, tokens or passwords)
- Install scripts
- None found
- Runs as
- Python package
Tools by what they do 17
Read from the source code; the running server may list different tools.
Read 8 · Look things up without changing anything.
gsc_cannibalizationgsc_compare_periodsgsc_indexing_issuesgsc_inspect_urlgsc_querygsc_quick_winsgsc_sitemapsgsc_sites
Delete 1 · Delete, drop, revoke or wipe things.
gsc_traffic_drops
Not yet classified 8 · We could not tell from the name and description.
gsc_alertsgsc_auditgsc_content_decaygsc_ctr_gapsgsc_doctorgsc_performance_overviewgsc_portfoliogsc_site_details
Secrets and settings it asks for
Secrets: values you paste in that let it act as you.
GSC_CLIENT_SECRETGSC_REFRESH_TOKEN
Other settings (environment variables or headers).
GSC_CLIENT_IDGSC_DATA_STATEGSC_REPORT_LANGUAGEGSC_SERVICE_ACCOUNT_FILE
Network hosts it talks to 8
accounts.google.com· found in codeanthropic.com· found in codedocs.astral.sh· found in codegithub.com· found in codeglama.ai· found in codegoogleapis.com· found in codeoauth2.googleapis.com· found in codesearchconsole.googleapis.com· found in code
Files it touches
- Your home directory (~)
Tools (17)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
gsc_alertsWhat changed sharply enough to be worth a message today. Compares the last `window_days` against the window before it across both queries and pages, and returns only movements past the alerting rules: lost positions, collapsed CTR, dropped or vanished pages.
gsc_auditBuild a complete, self-contained HTML SEO audit for one property. Collects the period and its baseline, top queries and pages, devices, countries, the daily trend, six months of history, sitemaps and an indexing check, then detects issues and builds a prioritised strategy and roadmap. Thresholds adapt to the size of the property, so small sites get a report too. Available in English and Italian. Ask the user for the period if they have not named one: the 28-day default is rarely what a client report wants. Returns a compact JSON summary first (KPIs with deltas, issue counts, top quick wins,…
gsc_cannibalizationQueries where several pages of the site compete for the same result. Reads one page of up to 25,000 query/page pairs; on a very large property the tail is cut off, and the meta says how many pairs were analysed. Each row lists the competing pages with their own clicks and positions.
gsc_compare_periodsJoin two periods on one dimension and rank the rows by click delta. Answers "what changed" without the model diffing two tables by hand. Rows present in only one period are kept, with zeros on the missing side; the biggest movers in both directions are returned, worst first. The meta counts how many rows gained and how many lost clicks.
gsc_content_decayPages sliding down month after month. A period comparison hides this: a page that halves over six months never shows a sharp drop in any single month-on-month check. One query per month runs in parallel.
gsc_ctr_gapsRows that rank well but are clicked far less than their position implies. The snippet, not the ranking, is the problem, which makes these the cheapest fixes available. `expected_ctr` is what a result at that position normally earns.
gsc_doctorReport the server's configuration and whether Search Console answers. Call this first when something fails: it names the auth mode in use, when the token expires, how many properties the account can read, the cache state and the defaults every other tool applies. Secrets are masked.
gsc_indexing_issuesCheck whether a batch of URLs is indexed, and why not when they are not. Runs the inspections concurrently and returns one row per input URL, in input order. A URL that fails gets an `error` column instead of a verdict; the rest of the batch still comes back. For the full payload of a single page (mobile usability, rich results, AMP) use `gsc_inspect_url`. Quota: 600 inspections per minute and 2,000 per day, per property. Columns: url, verdict (PASS / PARTIAL / FAIL / NEUTRAL), coverage_state, robots_txt_state, indexing_state, page_fetch_state, crawled_as, last_crawl_time, google_canonical,…
gsc_inspect_urlFull URL Inspection for one page: index, mobile, rich results and AMP. Use this when one page needs a diagnosis. For an indexed-or-not sweep across many URLs use `gsc_indexing_issues`. Quota: 600 inspections per minute and 2,000 per day, per property.
gsc_performance_overviewSite totals for a period, compared with the preceding one by default. Start here: it answers "is the site up or down" in one call, with the percentage change on every metric. `position_delta` is negative when the average position improves.
gsc_portfolioEvery accessible property at a glance, ranked worst first. One row per property with the current period, the previous one and a health flag: critical below -30% clicks, warning below -15%. Use it to decide which property to look at before running anything else.
gsc_queryQuery the Search Analytics report: clicks, impressions, CTR, position. This is the general-purpose tool. With no dates it covers the last 28 days ending today (UTC), with data_state=all so today's partial data is included, matching what the Search Console UI shows. Example: site_url="sc-domain:example.com", dimensions="query,page", period="last_28_days", row_limit=100. Returns a `# meta ...` line then a TSV table, or JSON with `meta` and `rows`. The meta names the exact range, the row count, whether more rows exist and the `start_row` to pass next.
gsc_quick_winsQueries close enough to the top that a push would pay off. Ranked by the clicks each query would gain at `target_position`, not by impressions: a big query already near its ceiling is not an opportunity. The meta reports the thresholds that were applied.
gsc_site_detailsPermission level and property type for one property.
gsc_sitemapsList the sitemaps Google knows about for a property, with errors and warnings. Read-only: submitting or deleting a sitemap needs the read-write scope, which this server never requests. Returns one row per sitemap: path, last submitted and downloaded timestamps, pending flag, index flag, warning and error counts, and the submitted / indexed URL counts when Google reports them.
Show 2 more tools
gsc_sitesList every property the authenticated account can read. Call this first when a property string fails: it returns the exact `site_url` values the other tools expect, and whether each one is a domain property (`sc-domain:example.com`) or a URL-prefix property.
gsc_traffic_dropsPages that lost clicks against the baseline, each with a likely cause. `diagnosis` separates a ranking loss from falling demand, a collapsed CTR and a page that disappeared: the four need different fixes, and the raw numbers for both periods are in the row so the call can be checked.
Signals
- Stars
- 9
- Forks
- 4
- Open issues
- 0
- Weekly downloads
- 601
- Last commit
- Oct 13, 2026 (16 days ago)
- Last release
- Aug 22, 2026 (2 months ago)
- Last package publish
- Aug 22, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.acamolese/google-search-console-mcp- Version
- 3.0.1
- Auth
- API key
- Packages
- pypi mcp-google-search-console
- License
- MIT
- First seen
- Oct 24, 2026
- Last checked
- Oct 25, 2026
Cite this page
Google Search Console MCP server. Agent Mart. https://agentmart.dev/connectors/acamolese-google-search-console-mcp (last updated 2026-10-25)