Google Search Console MCP server

Read from the package source without running it. The installed server may list more.

• add_property

  Add a property to this account (needs GSC_ALLOW_WRITE=1). Verification still happens in Search Console.

• brand_split

  Brand vs non-brand traffic. Give the brand in every script it is searched in, comma-separated (e.g. "toyota, تویوتا, トヨタ"). Each term matches its spelling variants, as whole words; with level=loose a term of 4+ characters also matches when glued to its neighbours (toyotacamry).

• build_query_regex

  Build a Search Console regex for a term that works in any script and matches its common spellings.

• compare_periods

  Compare a period with an earlier one; biggest movers first.

• content_movers

  Pages (or queries) that lost or gained ≥ threshold of their clicks vs an earlier period.

• data_freshness

  Which recent days are final and which are still changing, for daily and hourly data.

• delete_sitemapwrite action

  Remove a sitemap from Search Console (needs GSC_ALLOW_WRITE=1). The file itself is untouched.

• find_cannibalization

  Queries where two or more of your pages compete as separate results, ranked by impressions going to the non-best page.

• get_capabilities

  Auth status, scope, write access, history coverage and the list of tools. Call this first when unsure.

• get_property

  Details of one property (exact URL and permission level). Accepts loose input like example.com.

• get_sitemap

  Details of one sitemap: submission/download dates, errors, warnings, per-type URL counts.

• history_compare

  Compare two stored periods (e.g. this quarter vs the same quarter two years ago) — beyond the API's 16 months.

• history_query

  Query the local history for any date range, grouped by dimensions (queries merged across spellings).

• history_sqlwrite action

  Run a read-only SELECT on the history database. Table `rows` (site, search_type, date, query, qkey, page, country, device, clicks, impressions, position); `sync_days`. qkey is the multilingual match key.

• history_status

  What the local history contains: per property and search type, first/last day, rows, final days.

• history_trend

  Clicks/impressions/CTR/position per day, ISO week or month from the local history — any length of time.

• hourly_performance

  Hourly data for the last 10 days — Search Console's 24-hour view, and the only way to get true LOCAL days.

• indexing_summary

  Problems only: which of the given URLs are not indexed or have structured-data failures, and why. Up to 50 URLs.

• inspect_url

  Full URL Inspection for one page: index verdict, crawl, canonical, robots, sitemaps, rich results, mobile.

• inspect_urls

  Inspect up to 50 URLs in parallel (comma- or newline-separated). Quota is checked first.

• inspection_quota

  How many URL inspections this server has used today for a property (Google allows ~2,000/day).

• keyboard_mistypes

  Queries typed with the keyboard on the wrong layout (e.g. "ovdn lhadk" = «خرید ماشین» on a Persian keyboard).

• language_breakdown

  Share of clicks and impressions by the script/language of the query (Persian vs Arabic vs Latin…).

• list_properties

  List every Search Console property this account can see, with the permission level.

• list_sitemaps

  Sitemaps submitted for a property, with errors/warnings and URL counts. Pass sitemap_index to list its children.

• low_ctr_opportunities

  Query/page pairs on page one whose CTR is far below what their position should earn — title/snippet work.

• pages_for_query

  Which pages rank for one query — in each of its spellings — and how the impressions split between them.

• performance_overview

  One-screen summary: totals, trend, top queries and pages, devices, countries, and how fresh the data is.

• queries_for_page

  Which queries send traffic to one page. Spelling variants are merged unless group_variants=False.

• query_search_analytics

  Search Analytics rows with any dimensions and filters. The general-purpose query tool.

• query_variants

  Keywords that Search Console splits across several spellings, with their real combined totals.

• reauthenticate

  Forget the cached client and sign in again (switch Google accounts or scopes).

• remove_propertywrite action

  Remove a property from this account (needs GSC_ALLOW_WRITE=1). Data is not deleted at Google.

• striking_distance

  Queries ranking just off page one (default positions 8–20) with real demand — the quickest wins.

• submit_sitemapwrite action

  Submit (or resubmit) a sitemap URL (needs GSC_ALLOW_WRITE=1).

• sync_history

  Copy Search Analytics rows into the local SQLite history, one day at a time (keeps data past 16 months).

• top_terms

  Most demanded words across all queries — works for Chinese/Japanese/Thai (no spaces) too.

• Code scan22 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Google Search Console: common questions

Is Google Search Console MCP server safe?

Yes, by our scan: it is graded A (92/100). Read the Google Search Console safety report

How do I install Google Search Console?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Google Search Console need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Google Search Console maintained?

The last commit was 11 days ago (2026-10-02). The latest release is v0.2.2.

What can I use instead of Google Search Console?

Servers from other publishers that do the same job: Google Search Console MCP server, SEO Tools: Google Search Console MCP server and Gsc MCP server. Compare all Google Search Console alternatives.