MCP.Market

Google Search Console MCP server

by ni-c·io.github.ni-c/google-search-console-mcp·v0.3.0
No reviews yet

MCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

0 stars102 downloads/wk

Reviews

Write one

Nobody has reviewed Google Search Console yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Google Search Console tools (21, 6 write)

write = sends, deletes, buys or posts

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

  • add_site

    Adds a property to Search Console. This does NOT verify ownership:

  • delete_sitewrite action

    Removes a property from Search Console. Two-step: the first call

  • delete_sitemapwrite action

    Removes a sitemap from the property. Two-step: the first call returns a

  • get_indexing_status

    Returns when this credential last notified Google about a URL through

  • get_site

    Returns one property and the permission level this credential has on

  • get_sitemap

    Returns the full record for a single submitted sitemap: last submitted,

  • get_verification_token

    Returns the token that proves ownership of a site, and says exactly

  • get_verified_site

    Returns one verified site and the email addresses of all its owners.

  • inspect_url

    Asks Google what it knows about one URL: whether it is indexed, when it

  • inspect_urls

    Inspects up to … URLs of one property in a single call,

  • list_sitemaps

    Lists the sitemaps submitted for a property, each with when Google last

  • list_sites

    Lists every Search Console property this credential can see, with the

  • list_verified_sites

    Lists every site this credential has *verified ownership* of, with the

  • query_search_analytics

    Clicks, impressions, CTR and average position from Google Search,

  • request_indexing

    Tells Google through the Indexing API that a URL was updated or

  • setup_site

    Works out where a property stands and says exactly what to do next.

  • submit_sitemapwrite action

    Submits a sitemap URL, or resubmits one Google already knows.

  • submit_sitemapswrite action

    Submits up to

  • unverify_sitewrite action

    Removes this credential from the owners of a site. Two-step: the first

  • update_site_ownerswrite action

    Replaces the list of verified owners of a site. This is how a second

  • verify_site

    Tells Google to check for the verification token and, if it finds it,

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • Code scan51 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 qualitystatic API keys via environment variables6/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Google Search Console compares

Against every graded SEO MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 70% of 769 SEO servers
Tools
21
the typical SEO server has 6
Tools that change things
29%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
102
more than 62% of 170 SEO servers with a package

What its tools let an agent do: 13 read · 1 create · 5 change · 2 delete

Install Google Search Console in Claude Code, Cursor or VS Code

Runs npx -y @ni-c/google-search-console-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add google-search-console-mcp -- npx -y @ni-c/google-search-console-mcp
Add to Cursor

What the publisher says

From the Google Search Console repository's README, as published. We do not edit it. Read it on GitHub

google-search-console-mcp

<!-- badges: start -->

<!-- badges: end -->

A Model Context Protocol (MCP) server for Google Search Console, the service that tells you how Google sees your site — this reads it and sets it up.

Lets MCP clients like Claude Code, Claude Desktop or Codex create a property and prove ownership of it, submit and refresh sitemaps, ask what any URL's index status is, and query the whole Performance report — with the irreversible operations put to a person first and the write tools switchable off entirely.

21 tools is the ceiling, not the floor: GSCALLOWTOOLS=essential registers a curated five instead, and a model picks the right tool far more reliably from five than from 21 — see choosing which tools load.

What makes it different

It can actually create a working property. Getting one takes four steps in a fixed order — obtain a verification token, place it in DNS or on the page, verify ownership, add the property — and nothing in Google's APIs enforces that order. Calling sites.add first succeeds and leaves a property that appears in every listing and answers 403 for every piece of data, which looks like a permissions bug and is not. setup_site reports which step is missing and hands over the exact DNS record to paste. Servers that expose sites.add alone can only add properties somebody already verified by hand.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Google Search Console: common questions

Is Google Search Console MCP server safe?
Mostly: it is graded B (83/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?
Yes. The registry entry asks for GSC_SERVICE_ACCOUNT_KEY, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN.
Is Google Search Console maintained?
The last commit was 23 days ago (2026-10-12). The latest release is v0.3.0.
What can I use instead of Google Search Console?
Servers from other publishers that do the same job: SEO Skill MCP server, Google Ads + Meta Ads + SEO/GEO MCP server and SEO Tools: Google Search Console MCP server. Compare all Google Search Console alternatives.
How does Google Search Console compare with other SEO MCP servers?
safety score 83/100 (higher than 70% of 769 SEO servers); tools 21 (the typical SEO server has 6); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Google Search Console

Same job from other publishers: the closest match first, then the best rated.

All Google Search Console alternatives →
  • SEO Skill
    Free Google Search Console MCP: your real GSC, Google Analytics and keyword data for AI agents.
    A
  • Google Ads + Meta Ads + SEO/GEO MCP
    Google Ads, Meta Ads, Google Analytics (GA4) & Search Console MCP server by Ryze AI
    A
  • SEO Tools: Google Search Console
    Google Search Console: Search Analytics, URL Inspection, sitemaps (read-only, OAuth/service acct).
    More from antohins →
    B
  • MetricPort
    Google Search Console, Ads and AdSense analytics for AI clients. Hosted, read-only, 57 tools.
    A
  • Searchdock CLI
    Read-only Google Search Console analytics, URL inspection and sitemaps via SearchDock CLI.
    A

More from ni-c →