---
title: "Google Search Console MCP: How to Connect GSC to Claude, ChatGPT and Cursor"
description: "Google has no official Search Console MCP. I compared open-source servers, hosted connectors and Ahrefs: setup, where each works, cost and limits."
url: "https://rankbuddy.io/blog/google-search-console-mcp"
published: "2026-10-12T07:39:40.246Z"
updated: "2026-10-12T08:09:45.077Z"
---

Search interest in "Google Search Console MCP" has grown more than tenfold in a year. The reason is simple: once Claude or ChatGPT can read your Search Console, you stop exporting CSVs and start asking questions like "which pages lost clicks this month, and are they still indexed?"

The first thing most people look for is Google's own server, and there isn't one. So the real choice is between three routes: an open-source server you run on your computer, a hosted connector you add with one URL, or an SEO platform that already pulls your Search Console data.

I build RankBuddy, which is one of the hosted connectors, so I have a stake in this. For this guide I checked Google's list of official MCP servers, read the documentation of each option, and asked Claude real questions about my own site through RankBuddy. Where I am working from documentation rather than my own setup, I say so.

**Quick answer:** Google does not offer an official Search Console MCP server. If you are comfortable with Google Cloud and only use Claude Desktop or Cursor, a free open-source server such as **mcp-gsc** is the most complete option. If you want it in Claude on the web, in ChatGPT, or without setting up Google Cloud, use a **hosted connector** that connects Search Console with a normal Google sign-in. If you already pay for **Ahrefs** (Lite or higher), its MCP server can read the Search Console data you connected there.

***

## Is there an official Google Search Console MCP server?

No. Google publishes a [list of the MCP servers it runs](https://docs.cloud.google.com/mcp/supported-products). When I checked it in October 2026, it had 80 of them, from BigQuery and Cloud Run to Gmail and Google Drive. Search Console was not on it, and neither was Google Analytics.

Every Search Console MCP you will find is built by someone else on top of Google's public [Search Console API](https://developers.google.com/webmaster-tools). That is not a problem in itself: the API is free and well documented. It does mean you should check who runs the server, what access it asks for, and where your data goes.

***

## What Claude can do with a Search Console MCP

A Search Console MCP gives the assistant tools that call the same API behind the Search Console reports. In practice, that means three things:

* **Performance data:** clicks, impressions, CTR and average position, grouped by query, page, date, country or device, for any period in the last 16 months.
* **Index status:** Google's answer for a specific URL: indexed or not, why not, when it was last crawled, and which canonical Google picked.
* **Sitemaps:** which sitemaps are submitted and whether Google read them. Some servers can also submit or delete them.

What makes it useful is not the data itself, which you already have in Search Console. It is that Claude can join the pieces in one answer: compare two periods, find the queries that moved, check whether the affected pages are still indexed, and tell you what to look at first.

What it cannot do: change your rankings, see data older than about 16 months, or show you the queries Google hides for privacy. And Search Console data is usually 2 to 3 days behind, so "today" is never in the numbers.

***

## Three ways to connect Search Console to Claude: compared

Prices and details as listed on each product's own site in October 2026.

| Option                                                                            | Type                               | Works in                                                                       | Setup                                                                                                   | Search Console access                                         | Price                                                              |
| --------------------------------------------------------------------------------- | ---------------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------ |
| [mcp-gsc](https://github.com/AminForou/mcp-gsc)                                   | Open source, runs on your computer | Claude Desktop, Cursor, Codex, Gemini CLI. Not claude.ai or ChatGPT on the web | Google Cloud project, OAuth client or service account, config file                                      | Read; adding or deleting sites and sitemaps is off by default | Free                                                               |
| [suganthan-gsc-mcp](https://suganthan.com/blog/google-search-console-mcp-server/) | Open source, runs on your computer | Claude Desktop and other local clients                                         | Google Cloud project, OAuth client or service account                                                   | Read, plus the Indexing API if you enable it                  | Free                                                               |
| [RankBuddy](https://rankbuddy.io/mcp) (mine)                                      | Hosted                             | Claude web, desktop and mobile, Claude Code, ChatGPT, Cursor, VS Code          | Connect Search Console in the RankBuddy app with Google sign-in, then paste one URL into your assistant | Read-only                                                     | First question free, then a 7-day trial; from $29 a month          |
| ContextBolt SEO                                                                   | Hosted                             | Claude, Cursor, Codex                                                          | Google sign-in from inside the assistant                                                                | Read-only                                                     | $35 a month (1,000 credits); Search Console tools use no credits   |
| Porter Metrics                                                                    | Hosted                             | Claude web and desktop                                                         | Connect Search Console in Porter, then add a custom connector                                           | Read                                                          | Free after the trial for up to 3 properties and 30 days of history |
| Windsor.ai                                                                        | Hosted                             | Claude, ChatGPT, Cursor and other MCP clients                                  | Connect Search Console in Windsor, then connect its MCP                                                 | Read                                                          | Free plan available; check paid tiers                              |
| [Ahrefs MCP](https://docs.ahrefs.com/mcp/docs/introduction)                       | Hosted SEO platform                | Claude, ChatGPT and others                                                     | Connect Search Console in Ahrefs, then add Ahrefs from Claude's connector list                          | Read, plus Ahrefs' own data                                   | Ahrefs Lite at $129 a month and up; calls use API units            |

The trade-off is the same across the table. Open-source servers are free and give you the most Search Console tools, but you set up Google Cloud yourself and they only run where you can run a local process. Hosted connectors take a couple of minutes and work in the browser and in ChatGPT, but you pay for them and trust a third party with read access. Ahrefs makes sense only if you already pay for it.

***

## Way 1: an open-source server on your own computer

The most complete free option I found is **mcp-gsc** by Amin Foroutan, with about 1,300 GitHub stars. Its README lists tools for search analytics, period comparison, page and query breakdowns, URL inspection (single and batch), indexing issue checks and sitemaps. I did not install it for this article; the steps below are from its documentation.

1. **Create a Google Cloud project** and enable the Search Console API.
2. **Create credentials.** For personal use, an OAuth client of the "Desktop app" type: you download its JSON file, and the first run opens a Google sign-in in your browser. For automation or a team, a service account: you download its key and add the service account's email as a user on your Search Console property.
3. **Install the server.** The recommended way is with uv: you add a `gscServer` entry to your client's config that runs `uvx mcp-search-console` and points to your credentials file.
4. **Restart the client** completely and ask your first question.

Three things trip people up:

* **Domain properties need the prefix.** A domain property is `sc-domain:example.com`, not [`https://example.com/`.](https://example.com/.) Get it wrong and the server says you have no access.
* **The service account must be added in Search Console.** Creating it in Google Cloud is not enough.
* **Destructive tools exist.** mcp-gsc can add and delete sites and sitemaps, but only when you set `GSC_ALLOW_DESTRUCTIVE` to `true`. Leave it off unless you really need it.

Because the server runs on your machine, it works in Claude Desktop, Cursor and other local clients, not in Claude on the web or in ChatGPT. Suganthan Mohanadasan's **suganthan-gsc-mcp** follows the same pattern with 29 tools, including content decay and cannibalisation checks, and an optional Indexing API.

If you write code and want raw Search Console data for free, this is the route I would take.

***

## Way 2: a hosted connector

A hosted connector does the Google side for you. You connect Search Console once with a normal Google sign-in, and the assistant reaches it through one URL. Here is how it works with RankBuddy, the one I know best.

**1. Connect Search Console inside RankBuddy.** Add your site, then connect Search Console from the site's settings (or from the prompt the app shows you). You sign in with the Google account that has access to the property, approve read-only access, and pick the verified property to attach. There is no Google Cloud project, no service account and no config file.

![Connecting Google Search Console to a site in the RankBuddy app](https://rankbuddy.io/i/38f452e9-92cd-4c53-9e13-177b4829575d)

**2. Add RankBuddy to Claude.** In Claude, open **Customize**, then **Connectors**, choose **Add custom connector**, name it RankBuddy and paste `https://mcp.rankbuddy.io/mcp`.

![Adding RankBuddy as a custom connector in Claude with the URL mcp.rankbuddy.io/mcp](https://rankbuddy.io/i/0d540f14-6d00-48b2-a368-443313b6574a)

**3. Sign in to RankBuddy and allow access.** Claude never sees your Google or RankBuddy password, and every tool only reads data.

![RankBuddy's read-only permission screen when connecting it to Claude](https://rankbuddy.io/i/25a1db06-15f8-4fe8-86ba-069e2c10cc90)

**4. Turn it on in a chat and ask.** For example: "Using RankBuddy, which of my pages lost clicks in the last 28 days, and are they still indexed?"

The Search Console part of RankBuddy is two tools: one for performance data (by query, page, date, country or device, up to 90 days per call and about 16 months back) and one for URL inspection (up to 5 URLs per call). The same connector also brings keyword volumes, Google's current top 10, competitor keywords and backlinks, which is the main reason to pick it over a Search Console-only server. One question in Claude uses one RankBuddy credit, however many tools Claude calls to answer it.

Where it is weaker: it has fewer Search Console tools than mcp-gsc (no sitemap management, no batch inspection of hundreds of URLs), and it costs money after the trial.

Other hosted options work the same way with different trade-offs:

* **ContextBolt SEO** connects Search Console through Google's consent screen from inside the assistant. Its Search Console tools are free; credits pay for its keyword and competitor data.
* **Porter Metrics** connects Search Console in Porter first. After the trial, its free tier covers up to 3 properties with 30 days of history.
* **Windsor.ai** streams Search Console and other marketing sources into Claude, ChatGPT and other assistants, with a free plan.

***

## Way 3: Ahrefs MCP with your Search Console connected

If you already pay for Ahrefs, you may not need anything else. The Ahrefs MCP server has a `gsc` tool group with keywords, pages, positions and performance history from the Search Console account you connected in Ahrefs. You add Ahrefs from Claude's connector list and sign in.

The catch is cost. The remote MCP needs a paid plan from Lite ($129 a month), and every call spends API units from your monthly allowance. For Search Console alone that is expensive. For a team that already lives in Ahrefs, it is the obvious choice because Claude gets Ahrefs' own data in the same chat.

***

## What I got when I asked Claude about my own site

To see what this looks like in practice, I asked Claude three questions about rankbuddy.io with the RankBuddy connector on. The site is young, so the numbers are small, and that turned out to be useful.

**"How is the site doing in Google over the last 90 days?"** Claude pulled daily data and summed it: 9 clicks and 250 impressions from 13 July to 10 October 2026, at an average position of 22.8, with weekly impressions between 11 and 45. Its reading was the right one for a new site: visibility is still forming, and the sample is too small to judge click-through rates.

**"Which searches am I getting impressions for?"** The biggest real query was the brand, "rankbuddy", with 26 impressions at an average position of 7.3. The surprise was everything else. Several queries were clearly not people: long strings with `-site:reddit.com -site:youtube.com` operators, a "founder community" search with forty exclusions, and a keyword export from another company's SEO tool. These are scrapers and tools running queries through Google, and in a small property they make up a big share of the "queries". A dashboard shows them as demand. Asked directly, Claude separated them from real searches, and that is the kind of reading I want from an assistant.

**"Are my newest pages indexed?"** I asked Claude to inspect three URLs. My Claude SEO skills guide, published on 9 October, was already indexed and had been crawled the same day. My best SEO tools for SaaS article was indexed too. But the `/mcp` page, the one this very guide is about, came back as "URL is unknown to Google", even though it returns a normal 200 and is listed in the sitemap. I would not have spotted that without asking, and the fix is simple: request indexing for it in Search Console and link to it from pages Google already crawls.

All three questions together used three tool calls. If you want to understand why impressions rise while clicks stay flat on a site like this, I explain that gap in my guide to [GSC clicks vs impressions](https://rankbuddy.io/blog/gsc-clicks-vs-impressions).

***

## How to connect it in ChatGPT and Cursor

The rule is the same everywhere: **local servers only work in apps that can start a process on your computer. Web apps need a hosted server.**

**ChatGPT.** ChatGPT connects to remote MCP servers only, so an open-source server running on your laptop will not work in it. For a hosted connector, select **+**, then **Add custom MCP server**, name it, paste the URL and choose OAuth, then install it and sign in. On Pro, custom MCP servers need developer mode; on Business and Enterprise an admin may need to allow them first. The [RankBuddy MCP guide](https://rankbuddy.io/mcp) has the current steps with screenshots.

**Cursor.** Cursor takes both. For a hosted connector, add it to `~/.cursor/mcp.json`:

```json
{"mcpServers":{"rankbuddy":{"url":"https://mcp.rankbuddy.io/mcp"}}}
```

For a local server such as mcp-gsc, add the command and credentials path from its README to the same file instead.

**Claude Code.** One command adds a hosted connector: `claude mcp add --transport http rankbuddy `[`https://mcp.rankbuddy.io/mcp`](https://mcp.rankbuddy.io/mcp). Then run `/mcp`, pick it and sign in.

***

## Limits and safety

A few things are worth knowing before you rely on any of these.

* **Google's API limits apply to everyone.** The [Search Console API](https://developers.google.com/webmaster-tools/limits) allows 1,200 queries per minute per site, 2,000 URL inspections per day per site, and returns at most 25,000 rows per request. Hosted tools work within the same limits, usually by caching and paging.
* **Small sites get thin data.** With a few hundred impressions a month, CTR and average position describe a handful of searches, not your real rankings. A good assistant says so instead of drawing conclusions.
* **Check what access you grant.** Read-only access (Google's `webmasters.readonly` scope) cannot change anything in Search Console. Some servers ask for full access so they can submit or delete sitemaps. If you only want answers, read-only is enough.
* **Your data goes to the AI model.** Whatever the server returns is sent to Claude or ChatGPT as part of the conversation. A local server keeps the connection on your machine, but the answer still goes through the model.

***

## Which one should you use?

* **You write code and want it free:** mcp-gsc in Claude Desktop or Cursor. The Google Cloud setup is the slow part, and you only do it once.
* **You want it in Claude on the web or in ChatGPT, without Google Cloud:** a hosted connector. RankBuddy if you also want keyword volumes, Google's top 10 and competitor data in the same chat; ContextBolt, Porter or Windsor if you mainly want reporting.
* **You already pay for Ahrefs:** connect its MCP and your Search Console inside Ahrefs.
* **You want answers without asking at all:** an MCP only works when you open a chat. If you want a weekly review sent to you, that is a job for an SEO agent on a schedule, which is what the [RankBuddy app](https://rankbuddy.io/features/google-search-console) does with the same data.

Whichever you pick, give Claude a method as well as the data. My guide to [Claude SEO skills](https://rankbuddy.io/blog/claude-seo-skills) shows how to turn a check like "pages that lost clicks" into a repeatable skill, and the [Claude SEO page](https://rankbuddy.io/claude-seo) compares the main ways to give Claude SEO data. If you are still deciding between a chatbot, a data connector and an agent, start with my overview of [SEO chat tools](https://rankbuddy.io/blog/seo-chat-tools).

## Frequently asked questions

### Is there an official Google Search Console MCP server?

No. Google's list of the MCP servers it runs (80 in October 2026) does not include Search Console or Google Analytics. Every Search Console MCP is built by a third party on top of Google's public Search Console API, either as an open-source server you run yourself or as a hosted connector.

### How do I connect Google Search Console to Claude?

Use a Search Console MCP. With a hosted connector such as RankBuddy, you connect Search Console in the app with a Google sign-in, then add the connector URL in Claude under Customize, Connectors, Add custom connector. With an open-source server such as mcp-gsc, you create a Google Cloud OAuth client or service account and add the server to Claude Desktop's config.

### Is there a free Google Search Console MCP?

Yes. Open-source servers such as mcp-gsc and suganthan-gsc-mcp are free and the Search Console API costs nothing. You run them on your own computer and set up Google Cloud credentials yourself. Some hosted tools, such as Porter and Windsor, also have free tiers with limits.

### Does a Search Console MCP work in ChatGPT?

Only if it is hosted. ChatGPT connects to remote MCP servers, so a server running on your laptop will not work in it. Add a hosted connector with Add custom MCP server and OAuth; on Pro this needs developer mode, and on Business or Enterprise an admin may need to allow it.

### Can a Search Console MCP change my site or Search Console settings?

Read-only connectors cannot. Some open-source servers can add or delete sites and sitemaps; mcp-gsc keeps those tools off unless you set GSC_ALLOW_DESTRUCTIVE to true. None of them can change your rankings or your pages.

### How much Search Console data can Claude read?

The same as the Search Console API: about 16 months of performance data, up to 25,000 rows per request and 2,000 URL inspections per day per site. Data is usually 2 to 3 days behind, and Google hides some rare queries for privacy.

### What is the difference between a GSC MCP and Ahrefs MCP?

A GSC MCP reads your own Search Console. Ahrefs MCP reads Ahrefs' index and can also return the Search Console data you connected in Ahrefs, but it needs a paid plan from Lite at $129 a month and every call uses API units.
