Add mcp.gscwizard.com as a custom connector in Claude, sign in with Google once, and Claude reads your live Search Console data: clicks, impressions, position and CTR, plus finished analyses like decay, cannibalization and ranking changes.
Connector URL: https://mcp.gscwizard.com/mcp
The short answer
Claude reads Search Console through the Model Context Protocol. Pick the route that matches how you use Claude:
claude mcp add command with your API key.mcp-remote if you would rather use a static key than OAuth.Claude only ever sees the properties you connected in GSC Wizard, and access is revocable from your account.
A walkthrough of the same MCP server Claude connects to: adding it, signing in, and asking for real Search Console analysis in plain language.
The Connectors UI handles authentication for you with OAuth 2.1, so there is no key to copy, paste or rotate.
Sign in at tool.gscwizard.com with Google and choose the properties you want available. Claude never sees your Google credentials.
Open Settings → Connectors → Add custom connector, enter https://mcp.gscwizard.com/mcp as the URL, and leave the OAuth client ID and secret fields blank.
Claude registers itself, opens a Google sign-in and consent screen, and connects. The GSC Wizard tools then show up in the tools menu of any conversation.
Leave the OAuth fields blank. The GSC Wizard MCP server supports dynamic client registration, so Claude creates its own client. Filling in a client ID and secret is not needed and will get in the way.
One command adds the server to Claude Code, using an API key header rather than OAuth.
claude mcp add --transport http gsc-wizard \
https://mcp.gscwizard.com/mcp \
--header "Authorization: Bearer gscw_live_..."Create a key under Account → API keys in GSC Wizard. Keys look like gscw_live_..., carry a read-only or read-and-write scope, are shown once, and can be revoked at any time.
Run /mcp inside Claude Code to confirm the server is connected and see the tools it exposes.
The desktop config file launches local (stdio) servers only, so a "type": "http" entry is rejected as invalid. To use an API key instead of OAuth, bridge the remote server through mcp-remote (this needs Node.js). Open Settings → Developer → Edit Config, then add:
{
"mcpServers": {
"gsc-wizard": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://mcp.gscwizard.com/mcp",
"--header", "Authorization:${AUTH_HEADER}"
],
"env": { "AUTH_HEADER": "Bearer gscw_live_..." }
}
}
}The key goes in env rather than inline because mcp-remote splits each --header value on spaces, so Authorization:${AUTH_HEADER} is written without a space. On Windows, if npx fails to launch, set "command": "cmd" and prepend "/c", "npx" to args. Quit and reopen Claude Desktop fully after saving.
Every analysis runs server-side against the data warehouse, so the assistant reads a finished result instead of doing arithmetic over raw rows.
Most SEO connectors hand the raw rows back to the model. GSC Wizard does the opposite.
CTR curves, decay detection, cannibalization, opportunity scoring and full reports are computed server-side against the warehouse. Claude receives the finished result and reasons about it.
Because the heavy lifting never enters the context window, months of history and millions of rows stay in scope: a full SEO report over a 4 GB dataset in about 4.4 seconds.
Totals come from real queries, so there is no risk of a dropped row, a miscounted sum or an invented figure.
Read-only keys cannot call write tools at all. Read-and-write keys can, and every mutation is audit-logged. Revoke a key at any time from your account.
One Search Console connection, every assistant. Pick your client and follow the step-by-step guide.
The GSC Wizard app, a custom connector, or the Responses API.
Read the guideGemini CLI, Gemini Enterprise, and the Gemini API.
Read the guideA custom connector, an SEO analyst Bot, or Grok Build.
A custom MCP connector at grok.com/connectors, or the xAI API.
Read the guideThe endpoint, both auth modes, and a config for every client.
Read the guideSee also the Google Search Console MCP overview, the GA4 MCP, and the ChatGPT app.
No. Claude has no built-in Search Console integration. It reaches your data through an MCP connector: add the GSC Wizard MCP server at https://mcp.gscwizard.com/mcp and Claude can read the properties already connected to your GSC Wizard account.
In the Claude web and desktop Connectors UI, signing in is enough: the server supports OAuth 2.1 with dynamic client registration, so there is nothing to copy or store. Config-file clients such as Claude Code use an API key header instead.
Custom connectors live under Settings → Connectors on Claude's paid plans. Claude Code connects with a single command on any account that can run it, using an API key rather than OAuth.
The Claude Desktop config file launches local (stdio) servers only, so a remote HTTP entry is rejected as invalid. Use the Connectors UI (recommended) or bridge the remote server through mcp-remote, which needs Node.js.
Query search analytics, compare periods for ranking changes, find decaying content and cannibalization, model CTR against position, score opportunities, run URL inspections in bulk, read Bing Webmaster and GA4 data, manage topic clusters and content groups, submit URLs to IndexNow, and generate full SEO reports.
Yes. API keys carry a scope chosen at creation. A read-only key physically cannot invoke a write tool, so a read key makes the connection read-only by construction. Every mutation performed with a read-and-write key is audit-logged.
Yes. Claude Code takes one claude mcp add command. Cursor, VS Code (Copilot agent mode), Windsurf and any other MCP-capable client point at the same URL with an Authorization: Bearer header.
Add one connector URL and sign in. Claude then reads live data from the properties you already own, with nothing to export.