A Google Search Console MCP server lets Claude, ChatGPT, Cursor and other AI apps read your Search Console data, so you can ask “which pages lost clicks this week?” instead of opening reports. There are three kinds: open-source servers you run yourself, hosted servers you add by URL, and hosted servers made for many sites at once. Pick by where it runs, what access it asks Google for, and how many properties you need to compare.
We make allclicks, one of the servers below. Facts about the others are what their own sites said on 22 November 2026; links are in the table.
MCP (Model Context Protocol) is the standard way AI apps call outside tools. A Search Console server turns the Search Console API into tools the AI can call: list your properties, get clicks and impressions by query or page, inspect a URL. The AI then does the comparing, filtering and explaining for you. The data is the same you see in Search Console: about 16 months of history, with the last two or three days still changing.
| Run it yourself | Hosted | |
|---|---|---|
| Setup | Create Google Cloud credentials, install Python or Node, edit a config file | Paste a URL into the AI app and sign in with Google |
| Works in | Desktop apps and code editors on your computer | Also ChatGPT and Claude on the web and on phones |
| Your Google token | Stays on your computer | Kept by the service, ideally encrypted |
| Cost | Free (open source) | From free to a monthly plan |
| Updates | You update it | The service updates it |
Made for people with many sites. Ask once and see every property against the previous period, what is dropping, growing or new, and totals by tag. Goes deep on one site too: queries, pages, countries and devices with filters, up to 5,000 rows, Discover and Google News, URL inspection and an index audit with daily tracking. Comes with a free web dashboard of the same data, linked Google accounts and team workspaces.
The most starred Search Console MCP repository on GitHub (about 2,300 stars). You create your own OAuth client in Google Cloud and run it locally; read-only by default.
Every property your Google account can see, the full 16 months, read-only, five tools.
About 70 tools, reports that combine Google and Bing.
53 tools; says it archives Search Console history beyond Google's 16 months.
More than 130 tools, including content decay and cannibalization.
Five read-only tools on purpose; every search type, including Discover and Google News, and hourly data.
Part of a larger set of paid SEO MCP servers (SERP, keywords, backlinks).
There are many more: the official MCP Registry lists about thirty Search Console servers. These are the most visible ones we found, in no particular order after our own.
allclicks began as a free dashboard for people who run many sites, and its MCP server thinks the same way. Ask “which of my 40 sites dropped this week, and on which queries?” and you get one answer, not forty. Group sites with tags (a country, a client, a niche) and ask about the group as if it were one site. Track indexing every day and hear when pages drop out. Open the same numbers in the web dashboard when a chart says more than a chat. It is free, for any number of sites, and it asks Google only for read access.
Pick something else if you need Google Analytics or Bing data in the same place (GSC Magic, GSC PAP or GSC Wizard cover those), history older than Google’s 16 months, or a server that runs entirely on your computer (mcp-gsc).
To connect it, add https://app.allclicks.net/mcp as a custom connector and sign in with Google. Steps for each app are on the allclicks MCP server page.
A small service that lets an AI app such as Claude, ChatGPT or Cursor read your Search Console data through the Model Context Protocol, so you can ask about clicks, queries, pages and indexing in plain words instead of opening reports.
We did not find one from Google as of the date on this page. The servers you can use today are made by independent developers and companies, so check what access each one asks for.
Run one yourself if you want nothing to leave your computer and you are comfortable creating Google Cloud credentials. Use a hosted one if you want to add a URL and sign in with Google, or if you use ChatGPT or Claude on the web, which connect only to servers on the internet.
Only if it asks Google for write access. A server that requests the read-only scope (webmasters.readonly) can read your data but cannot submit sitemaps, remove URLs or change settings. You see the requested access on Google's consent screen.
Most servers answer about one property at a time, so comparing twenty sites means twenty calls. allclicks was made for that case: one call returns every property against the previous period, and tags add groups of sites up.
It differs. Read each privacy policy: what is stored, for how long, and whether your Google token is encrypted. allclicks keeps short-lived encrypted caches and an encrypted token per connection; details are in its privacy policy.