Google Search Console MCP

Google Search Console MCP is a free MCP server that gives your AI agent six Search Console tools. You can ask which searches bring people to your site, whether a page is indexed, and which sitemaps Google has on file, then act on the answer in the same session. It is its own VS Code extension, it runs on your machine, and it talks to your own Google account.

There is no server to host and no config file to edit. You install the extension, sign in to Google once, and the tools appear in every agent it finds: VS Code Copilot, Claude Code, Cursor, OpenAI Codex, Google Gemini, Windsurf, Continue.dev, and Cline.

What you can ask

  • “What are my top 20 searches for the last 28 days?”
  • “Which pages lost clicks this month compared with last month?”
  • “Which searches am I ranking 8 to 20 for?”
  • “Is this URL indexed by Google?”
  • “Show me the sitemaps for my site”
  • “Submit the new sitemap”

The six Google Search Console MCP tools

Tool What it does
gsc_list_sites List every Search Console property your account can open
gsc_search_analytics Query clicks, impressions, click-through rate, and position
gsc_inspect_url Inspect one URL: index status, crawl details, mobile usability, and rich results
gsc_list_sitemaps List the sitemaps submitted for a property
gsc_submit_sitemap Submit a sitemap
gsc_add_site Add a property, as a URL prefix or a domain

What the search analytics tool can do

gsc_search_analytics is the one you will use most. It is the same data as the Performance report, without the 1,000 row limit of the screen.

Option What it accepts
Date range A start and end date
Group by Query, page, country, device, search appearance, date, or several at once
Search type Web, image, video, news, Discover, or Google News
Filters Any dimension, for example only pages under /blog or only one country
Rows 1,000 by default, up to 25,000 per call, with paging beyond that
Freshness Final data only, or including the most recent partial days

Because the agent can group by query and page together, it can answer questions the screen makes awkward, such as which two pages compete for the same search.

Three things people use it for

Finding pages that are close to page one

Ask for searches where your average position is between 8 and 20 with a reasonable number of impressions. Those are the pages where a better title or a clearer answer has the most effect. The agent returns the list with the page for each search.

Checking a page after you publish

Publish, then ask whether the URL is indexed. gsc_inspect_url returns what Google last saw. That covers whether it is on Google, when it was crawled, which canonical Google chose, and whether the page was fetched successfully.

Fixing what the data shows, in the same session

This is the reason to have Search Console in a coding agent. The agent reads the weak title in the report, opens the template or the content file, and proposes the change. You do not carry numbers between a browser tab and an editor.

Set it up in five steps

A setup wizard opens the first time you launch the extension. Most people pick OAuth, which works with a personal Google account.

  1. Create a project in the Google Cloud Console, or pick one you already have.
  2. Enable the Google Search Console API under APIs and Services.
  3. Create an OAuth client ID of type Desktop app.
  4. Paste the client ID and secret into the wizard.
  5. Sign in to Google in the browser window that opens, and authorize.

If your consent screen is set to External, add yourself as a test user first. Developers who already use the gcloud CLI can pick Application Default Credentials instead. With a service account key, add the service account’s address as an owner of each property under Settings, Users and permissions. The account you sign in with has to be a user on the property in Search Console, or its properties will not appear.

Property names: URL prefix or domain

The tools take the property exactly as Search Console names it. A URL prefix property looks like https://example.com/, with the trailing slash. A domain property looks like sc-domain:example.com. If a call fails with “not found”, this is usually why. gsc_list_sites shows the exact strings.

Using Google Search Console MCP with Claude Code, Cursor and other agents

You do not add a server entry by hand. The extension writes the registration for each agent it finds: ~/.claude.json for Claude Code, ~/.cursor/mcp.json for Cursor, ~/.codex/config.toml for OpenAI Codex, ~/.gemini/settings.json for Gemini, and the matching files for Windsurf, Continue.dev, and Cline. VS Code Copilot picks it up through the VS Code API.

Open a new session in any of them and the tools are in the tool list. To limit which agents get them, switch the others off in VS Code settings under gscMcp.agents. The command “Google Search Console MCP: Remove from All Agents” takes every registration back out.

Two Indexing API tools

The extension also has two tools for Google’s Indexing API. indexing_notify tells Google a URL was updated or removed, and indexing_status shows the last notification for a URL. They need a service account with the indexing scope, added as an owner of the property. Asking Google to remove a URL needs confirm: true. Google documents the Indexing API for job posting and livestream pages, so use it for those page types.

Limits

  • Search Console data is two to three days behind. The agent sees what the Performance report sees.
  • URL inspection reports Google’s indexed version. It does not run a live test and it does not request indexing.
  • Adding a property does not verify it. You still prove ownership in Search Console.
  • Google hides rare searches for privacy, so query rows do not add up to the property total.

Common questions

Is Google Search Console MCP free?

Yes. The extension is free and MIT licensed, and Google does not charge for the Search Console API.

Does it work with Claude Code and Cursor?

Yes. Both are registered automatically, along with Copilot and five other agents.

Do I need Google Analytics to use it?

No. This extension is Search Console only. If you want Google Analytics reports in the same agent, GA4 Analytics MCP has the GA4 tools and these Search Console tools together.

Can it see all my sites?

It sees every property the signed-in account can open in Search Console, including ones other people have shared with you.

Where does my search data go?

Nowhere except Google. The MCP server runs on your own machine and calls Google’s APIs with your credentials. There is no telemetry, and the sign-in token is kept in VS Code’s encrypted secret storage.

Install it

Google Search Console MCP is free and MIT licensed. It is its own extension. If you also want Google Analytics, install GA4 Analytics MCP instead, which includes these Search Console tools. Install one or the other, because both register the same tools.

Related