The short answer
A Google Search Console MCP server is a small service that sits between your Search Console account and an AI assistant such as Claude, ChatGPT or Cursor. When you ask a question like “which pages lost clicks this month?”, the assistant calls the server, the server queries the Search Console API with your permission, and the assistant answers using the numbers that came back.
Nothing about your data changes. Search Console is still the source of truth. What changes is the interface: instead of filtering the Performance report, exporting 1,000 rows to a spreadsheet and pasting it into a chat, you ask in plain English and get an answer grounded in live data.
GSC MCP Server does this for both Google Search Console and Bing Webmaster Tools, across multiple accounts and properties, and it works in any assistant that speaks the Model Context Protocol.
What MCP actually is
The Model Context Protocol (MCP) is an open standard, introduced by Anthropic in late 2024, for connecting AI applications to outside tools and data. Think of it as a universal adapter. A service describes the tools it offers (their names, what they do, and which inputs they accept), and any MCP-compatible assistant can discover and call them.
Before MCP, every AI app needed its own custom integration for every data source. With MCP, one server works across Claude, ChatGPT, Cursor, VS Code, Windsurf, Cline and others. That is why a single Search Console MCP server can serve a marketer in ChatGPT and a developer in Cursor at the same time.
How a request flows
- You ask your assistant a question about your site.
- The assistant decides it needs data and picks a tool, for example
get_search_queries, with inputs such as a date range and property. - The MCP server checks your authorization and calls the Search Console or Bing Webmaster API.
- The server returns structured results: clicks, impressions, CTR, average position and so on.
- The assistant reads the results and answers, often calling more tools to dig deeper.
The problem it solves
Search Console is the most accurate source of organic search data you have, and it is free. It is also slow to interrogate. A few everyday frustrations:
- The 1,000-row ceiling. The Performance report and its exports show at most 1,000 rows. Mid-sized sites routinely have tens of thousands of queries, so the long tail stays hidden unless you use the API.
- Questions that span filters. “Which queries moved from page two to page one, on mobile, in the UK?” takes several filter changes, a comparison and some spreadsheet work.
- Multiple properties. Consultants and agencies switch between dozens of properties, and Google and Bing data live in two different tools.
- Interpretation. Even after you have the numbers, turning them into a prioritised plan is a separate job.
An MCP server handles the fetching through the API (which reaches far beyond 1,000 rows), and the assistant handles the slicing, comparing and explaining.
What you can ask
These are typical questions people run in their first week. Each one maps to one or more tool calls.
Compare the last 28 days with the previous 28 days for my main site. Which ten pages lost the most clicks, and what queries drove the drop?
Show queries where I rank between positions 8 and 20 with at least 500 impressions. Group them by landing page and suggest what to improve on each page.
Is /pricing indexed? What canonical did Google choose, and when was it last crawled?
For every client account, give me clicks, impressions and CTR for last month and the change from the month before, as a table.
For deeper versions of these workflows, see our guides on striking distance keywords, diagnosing a traffic drop and agency client reporting.
The tools behind the answers
GSC MCP Server exposes a focused set of read-only tools. Your assistant chooses between them automatically, but knowing what exists helps you ask better questions.
| Tool | What it returns | Source |
|---|---|---|
list_search_properties | Connected accounts and the properties each can access | Google, Bing |
get_search_overview | Clicks, impressions, CTR, average position and daily clicks | Google, Bing |
get_search_queries / get_search_pages | Top queries and landing pages, sorted by clicks | Google, Bing |
get_search_opportunities | Low-CTR queries and “striking distance” queries at positions 8–20 | Google, Bing |
compare_search_periods | Period-over-period or year-over-year winners and losers | Google, Bing |
query_search_analytics | Custom reports by query, page, country, device, date and search appearance, with filters and pagination | |
find_keyword_cannibalization | Queries where two or more of your pages compete | |
inspect_url | Index verdict, coverage, last crawl, canonicals and rich results for one URL | |
list_sitemaps | Submitted sitemaps and feeds with error and index counts | Google, Bing |
get_bing_crawl_stats | Pages crawled, crawl errors, status codes and index size | Bing |
multicall | Several of the above in a single request | Both |
MCP vs exports, Looker Studio and SEO suites
An MCP server does not replace every tool you use. It fills a specific gap: fast, conversational access to first-party search data.
| Approach | Strength | Weakness |
|---|---|---|
| Search Console UI and CSV export | Free, official, no setup | 1,000-row cap, manual filtering, one property at a time |
| Looker Studio dashboards | Good for recurring visual reports | Answers only the questions you designed it for; slow to change |
| Third-party SEO suites | Competitor data, backlinks, rank tracking | Rankings and traffic are estimates, not your first-party clicks |
| BigQuery bulk export | Complete, unsampled history beyond 16 months | Requires SQL and a Google Cloud project |
| Search Console MCP server | Ad-hoc questions in plain language, Google + Bing together | Bound by API limits and the 16-month retention window |
Many teams pair them: an SEO suite for competitive research, a dashboard for stakeholders, and an MCP server for the daily “why did this happen and what should I do?” questions.
Who gets the most out of it
- Freelance SEO consultants who manage several sites and want to move from data gathering to recommendations faster.
- Agencies producing monthly reports across many client properties. See our agency reporting workflow.
- SaaS and startup founders who own SEO alongside ten other jobs. Our 30-minute weekly routine is written for you.
- Content marketers and editors who need to know which articles to refresh and which overlap. Start with keyword cannibalization.
- Developers who want indexing and canonical checks next to their code. Read technical SEO in Cursor and VS Code.
Access, privacy and read-only scopes
You connect Google and Bing through their own OAuth consent screens, so you never hand over a password. GSC MCP Server asks only for read-only access to search data. AI clients then connect to the server with their own scoped, revocable authorization, so you can disconnect ChatGPT without disconnecting Claude.
Your AI provider will see the data the assistant retrieves during a conversation, the same as if you had pasted a report into the chat. If your organisation has rules about which assistants may handle client data, apply them here too. Teams with stricter requirements can self-host the open-source server. Our privacy policy explains what the hosted service stores.
Limits worth knowing
An MCP server inherits the limits of the APIs underneath it. These are the ones that shape answers most often:
- 16 months of history. Search Console keeps performance data for 16 months. Year-over-year comparisons work; two-year trends do not, unless you archive data yourself.
- Anonymised queries. Google omits queries searched by very few people to protect privacy, so query-level totals are usually lower than page-level totals. This is expected, not a bug.
- Data freshness. Final data typically lags by two to three days. Very recent days may change.
- URL Inspection quota. Google allows around 2,000 inspections per property per day, so inspect important URLs rather than entire sites.
- AI features in the totals. Impressions and clicks from AI Overviews and AI Mode are counted inside the Web search type, not reported as a separate channel in the main Performance report.
How to get started
- Create a free account with Google or GitHub.
- Connect a Google Search Console or Bing Webmaster Tools account and pick the properties you want available.
- Add the server to your assistant. Our setup guide for Claude, ChatGPT, Cursor and VS Code walks through each client.
- Ask a first question, such as “What changed in my search traffic this month?”
The free plan covers one Google or Bing account and 30 tool calls a month, which is enough to see whether this way of working suits you. Paid plans are listed on our pricing section.
Frequently asked questions
Is there an official Google Search Console MCP server?
Google has not published an official Search Console MCP server. The servers in use today, including GSC MCP Server, are built on the public Search Console API, which means they return the same data you see in Search Console, subject to the same limits.
Does an MCP server change my Search Console data?
No. GSC MCP Server requests read-only access. It can read performance data, sitemaps and URL Inspection results, but it cannot submit sitemaps, remove URLs, add users or change settings.
Which AI assistants support MCP?
Claude (web, desktop and Claude Code), ChatGPT through custom connectors, Cursor, VS Code with GitHub Copilot, Windsurf, Cline and a growing list of other clients support MCP. Setup differs slightly between them.
Can the AI make up numbers?
Any language model can misstate figures, which is why tool calls matter: the assistant fetches the numbers from Search Console instead of guessing. Good practice is to ask it to show the table it used and to spot-check important figures in Search Console.
Do I need to be technical to use it?
No. With the hosted version you sign in, connect Google or Bing, and paste one URL into your AI app. Self-hosting is available for teams that want to run the server themselves.