Google Search Console MCP server

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,

• 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 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?

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, Claude Desktop or Cursor 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 in the last day (2026-09-19). 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: Google Search Console MCP server, Google Search Console MCP server and Agency MCP server. Compare all Google Search Console alternatives.