The Google Search Console MCP is the ZeusSEO connector for Claude. Paste one link into your AI assistant and it can reach the Search Console insight ZeusSEO already holds for your clients, with no separate Google Search Console API application to file yourself.
Search Console is where the truth about a client's organic visibility lives: which queries they show up for, which pages earn clicks, and where indexing quietly breaks. The slow part has always been access. The official Search Console API makes you register an app, justify the use case, and pass verification before you can read a single row.
ZeusSEO already did that work. It is a Google-verified app that connects Search Console for you and pulls that data into its reports. Connecting the ZeusSEO connector puts that context one message away in Claude, and every new Search Console tool we ship arrives at the same link with nothing new to add.
It is the same one connector you already use to publish Google Business Profile posts and to reach your Google Analytics data, so one connection covers every Google source you report on.
The Google Search Console MCP is the ZeusSEO connector exposed to AI assistants through the Model Context Protocol. It is one link you paste into Claude once. Because ZeusSEO is already an authorized Google app that reads your Search Console data for its reports, the connector is your assistant's doorway to that Search Console context, without you building or verifying a Google API integration of your own.
Connect it in 3 steps
Go to Claude
This link opens Claude's "Add custom connector" dialog directly:
Prefer to navigate by hand? In Claude: Settings → Connectors → Add custom connector.
Paste the link, click Add, then Sign In / Register
Name it anything, ZeusSEO works, and paste this server URL. It is the only address you ever need, for everything ZeusSEO can do:
If you expand Advanced settings you will see OAuth Client ID and OAuth Client Secret fields, leave both empty. ZeusSEO does not use one; the connection registers itself the moment you click Add.
The moment you click Add, Claude sends you straight to Google's own account picker, with no ZeusSEO screen in between. This is where you Sign In or Register: choose the Google account whose Search Console data you want to reach, and if it is an account you have not used with ZeusSEO before, this same step registers it. You can stay signed into Claude with one email and pick a different Google account here; they do not need to match.
Turn on every permission
When Claude lists the tools this connector offers, switch all of them on, not only some. That way your assistant can use every ZeusSEO ability the moment it lands, including the Search Console tools as they ship.
Confirm it worked. Start a new chat and ask:
Which clients and saved reports do I have in ZeusSEO?
If it comes back with your real client names and reports, you are connected. If it cannot see them, open Troubleshooting below.
- One ZeusSEO connector link covers Search Console and every other ZeusSEO ability, on every plan including the free trial.
- You skip the Google Search Console API application entirely, because ZeusSEO is already a verified Google app.
- Today the connector reaches your Search Console context through your ZeusSEO reports and clients; direct per-query reads are on the way to the same link.
- Setup is the same three steps: open Claude, paste the link and click Add, then Sign In or Register with Google.
- Your Google credentials never reach the AI assistant. Claude talks to ZeusSEO, and ZeusSEO talks to Google.
What you can do today, and what is coming
ZeusSEO keeps a clear line between what is live and what is next, so you never promise a client a number the tool cannot yet pull.
Available now
- List your clients and match them by name, so your assistant knows which business you mean.
- List the saved ZeusSEO reports you have built for each client, the reports where your Search Console data already lives.
- List your scheduled report deliveries, so you can see what is set to send and when.
Coming to the same connector
Direct Search Console reads inside chat are in active development and will arrive at the same link you added, with nothing new to set up:
- Per-query performance: clicks, impressions, click-through rate, and average position by query and by page.
- Coverage and page-indexing issues, so your assistant can tell you which pages Google is struggling to index.
Until those ship, treat the connector as the fast doorway to the Search Console context ZeusSEO already maintains, not as a live query console. We announce each new tool inside ZeusSEO the moment it is live.
What an MCP is
MCP, the Model Context Protocol, is a standard way for a tool like ZeusSEO to hand a set of specific abilities to an AI assistant like Claude. In this case it is the ability to reach the Search Console context ZeusSEO holds for your clients. It is an open standard that Anthropic introduced in November 2024 (Model Context Protocol documentation, modelcontextprotocol.io).
You do not need to understand the standard to use it. You paste one web address into your assistant once, approve the connection, and from then on your assistant can do ZeusSEO work when you ask. That one address, https://app.zeuseo.com/api/mcp, is the whole connection, and anything ZeusSEO opens up later arrives at the same place.
Why go through ZeusSEO instead of the Search Console API
The official Google Search Console API is powerful, but getting to it is the slow part. You register your own Google Cloud project, request access, justify the use case, and pass OAuth verification before you read a single row, and Google can delay or decline that request. Then you own the quotas and the token refresh forever.
ZeusSEO is already a Google-verified app with that access in place. You connect once and inherit the authorized path, so there is no application to file, no verification to wait on, and no quota to manage on your side. For the full argument, read Google API vs MCP.
What it costs
Using the connector is free. It is included on every plan, the free tier, the trial, and every paid plan alike. There is no separate charge to use the connector and no plan that unlocks it over another.
Reading your own Search Console data through Google is free to you, the same way it is inside ZeusSEO's reports. If a future tool asks ZeusSEO's own AI to analyze that data for you, that specific action spends Staters and tells you the cost first. The rule never changes: your AI does the thinking for free, our AI costs Staters. Every action is itemized in Credits → History, including the ones that cost zero.
Safety and permissions
How your data and access stay protected
Your Google credentials never reach the AI assistant
Claude talks to ZeusSEO, and ZeusSEO talks to Google. Your Google access token stays on ZeusSEO's servers and is never sent back to the assistant, to Anthropic, or to anyone else.
Read tools versus write tools
Listing clients, reports, and deliveries is read-only and may run without a prompt, which is intentional, since looking at your own data is not a risk. Anything that changes data or spends Staters is marked so your assistant stops and asks you first.
How to revoke
Two independent switches. From the assistant: Settings → Connectors and remove ZeusSEO. From ZeusSEO: Settings, the Claude and ChatGPT section, and revoke the key. Revoking in ZeusSEO cuts access immediately.
Set up ChatGPT
ChatGPT support is coming. For now the ZeusSEO connector launches on Claude only. When ChatGPT is ready it will use the same connection and the same URL you already added, with nothing new to set up. Check back here, or watch for the announcement inside ZeusSEO.
Troubleshooting
"It cannot see my clients or reports."
The connector can only see what ZeusSEO already sees. Log in at app.zeuseo.com and confirm your clients and their Search Console connection show up there. If ZeusSEO's own Google connection has expired, reconnect it there first. That is a separate connection from the one you made to Claude, and fixing one does not fix the other.
"I asked for query numbers and it could not pull them."
Direct per-query Search Console reads are not a live tool yet. Today the connector lists your clients, saved reports, and scheduled deliveries. Open the report in ZeusSEO for the underlying Search Console numbers while the direct tools are being built.
"It is asking me to reconnect."
Either the connector's authorization expired or was revoked, in which case reconnect from your assistant's Connectors settings, or ZeusSEO's own Google connection expired, in which case log into app.zeuseo.com and follow the reconnect banner. Check ZeusSEO first; if your data is missing there too, it is the second one.
Getting started
The connector is included on every ZeusSEO plan and during the free trial. There is nothing to enable and nothing extra to buy. Reading your data costs no Staters, because you are spending your own AI subscription, not ZeusSEO's.
If you do not have an account yet, plans are at zeuseo.com/pricing.