How to Connect Google Search Console to Claude (Web, Desktop and Claude Code)
Connect Google Search Console to Claude in about a minute: add the hosted Search Console MCP as a connector on claude.ai or Claude Desktop, or run one command in Claude Code. Sign in with Google — no code, no API keys.
Claude will happily explain SEO theory forever. Connect it to Google Search Console and it starts answering with your numbers instead: your queries, clicks, impressions and positions, straight from Google. The connection is one URL through the hosted Search Console MCP — no code, no API keys, no Google Cloud project. It takes about a minute whether you use claude.ai in the browser, the Claude desktop app, or Claude Code in the terminal.
What you need
- A Claude plan that supports custom connectors (Pro, Max, Team or Enterprise on claude.ai; on Team and Enterprise an admin may need to enable them). Claude Code works with the same paid plans or an API key.
- A Google account with access to the Search Console property you want to query.
- That's it. The MCP server is hosted and read-only; nothing gets installed.
Option 1 — claude.ai and Claude Desktop (connectors)
- Open Settings → Connectors. On claude.ai that's your profile menu → Settings → Connectors; the desktop app has the same section.
- Add a custom connector. Click Add custom connector, name it something like Search Console, and paste the server URL:
https://mcpsearchconsole.com/mcp. - Sign in with Google. Claude opens a Google window; approve the read-only Search Console scope. That's the whole authentication — the server uses OAuth, so there is no API key to create or paste.
- Verify it. Start a new chat, make sure the connector is enabled in the tools menu, and ask: "List my Search Console properties." If your sites come back, you're connected.
Option 2 — Claude Code (one command)
In a terminal, run:
claude mcp add --transport http search-console https://mcpsearchconsole.com/mcpThen start claude, type /mcp, pick search-console and follow the Google sign-in. The OAuth flow completes in your browser and the token is stored locally; every future session is already connected. Ask "list my Search Console properties" to confirm.
From then on Claude can call the server's tools on demand: search performance with filters and period comparisons, URL inspection, sitemaps, PageSpeed and site-health checks. Everything is read-only by design, so Claude can analyze your site but never change anything.
What to ask once it's connected
Using a different assistant? The picker below has the same one-minute setup for ChatGPT, Cursor, Codex and more.
Connect Google Search Console to Claude
- Open Settings → Connectors in Claude Desktop or claude.ai.
- Click Add custom connector and paste the URL below.
- Click Add, then sign in with Google when prompted.
https://mcpsearchconsole.com/mcpConnect Google Search Console to Claude Code
Add the server from your terminal:
claude mcp add --transport http search-console https://mcpsearchconsole.com/mcpRun /mcp inside Claude Code and complete Google sign-in.
Connect Google Search Console to ChatGPT
- Go to Settings → Connectors and enable Developer mode.
- Click Create / Add custom MCP server and paste the URL below.
- Authenticate with Google to finish.
https://mcpsearchconsole.com/mcpConnect Google Search Console to Codex
Add this to ~/.codex/config.toml:
[mcp_servers.search-console]
url = "https://mcpsearchconsole.com/mcp"On Google sign-in, Codex opens your browser to authorize. (If your Codex version only supports stdio servers, bridge it with npx mcp-remote https://mcpsearchconsole.com/mcp.)
Connect Google Search Console to Mistral Vibe
- In Mistral Vibe → Settings → Connectors, choose Add MCP connector.
- Paste the URL below and save.
- Sign in with Google when prompted.
https://mcpsearchconsole.com/mcpConnect Google Search Console to Cursor
Add to ~/.cursor/mcp.json (or Settings → MCP → Add server):
{
"mcpServers": {
"search-console": { "url": "https://mcpsearchconsole.com/mcp" }
}
}Reload, then authorize with Google from the MCP panel.
Connect Google Search Console to any MCP client
Any client that supports remote MCP servers over Streamable HTTP. Point it at the URL and it handles Google sign-in via OAuth.
{
"mcpServers": {
"search-console": { "type": "streamable-http", "url": "https://mcpsearchconsole.com/mcp" }
}
}Troubleshooting
- No "Add custom connector" button. Custom connectors need a paid Claude plan, and on Team/Enterprise workspaces an admin has to allow them first.
- Claude doesn't use the connector. Tools are per-conversation: check the tools menu in the composer, toggle Search Console on, and mention it explicitly the first time you ask.
- Google sign-in loops or closes. Allow pop-ups for claude.ai and retry; the OAuth window must complete in the same browser session.
- Empty results for your site. Ask Claude to list your properties first.
sc-domain:example.comandhttps://example.com/are different Search Console properties; queries must use the exact one. - "Yesterday" looks empty. Search Console data trails by about two days. Ask for trailing windows (last 7 or 28 days) instead of yesterday.
Quota and pricing
Connecting is free: discovery and site-health tools are unlimited, and data pulls (performance queries, URL inspection, sitemaps, PageSpeed) are metered per day, week and month on the free plan. Occasional analysis fits comfortably; if you run daily reporting or an agent on top, Solo removes the caps for a few euros a month.
Go further
Once the connection works, the interesting part is what you do with it: our seven MCP workflows for SEO turn these prompts into a repeatable practice, and if your team lives in ChatGPT too, the ChatGPT guide is the same setup on the other side. For what to stack next to Search Console — backlinks, crawling, conversions — see the best SEO MCP servers comparison.
Ready to put your search data in your AI?
Set up the Search Console MCP, free