Connecting AI assistants
Ask Claude, ChatGPT, Gemini, Codex, Grok, Copilot or any other MCP client about your own Search Console, GA4, Bing, Yandex and Merchant Center data, and get answers from real numbers instead of guesses.
GSC Wizard runs a hosted MCP server (Model Context Protocol, the open standard assistants use to call outside tools) at https://mcp.gscwizard.com/mcp. You add that one address to your assistant and sign in, and the assistant can call more than 130 tools: performance summaries, top queries and pages, ranking changes, content decay, cannibalization, opportunity scoring, URL inspection, IndexNow, forecasts, GA4 reports, Bing and Yandex data, and the Merchant Center reports. The analysis runs on GSC Wizard’s servers over the full history in its data warehouse, so the assistant receives a finished result rather than thousands of raw rows to add up, which is faster, cheaper in tokens, and far less likely to produce a wrong total.
Pick your assistant
Every guide walks through one client from the first click to a first answer. The server, the sign-in and the tools are the same in all of them; only the place you paste the address differs.
Claude
A custom connector in the Claude app, the plugin or one command in Claude Code, the Desktop config file, or the Agent SDK.
ChatGPT
The GSC Wizard app from the ChatGPT App Store, a developer-mode connector with every tool, or the Responses API.
Codex
Search Console data next to your code in the Codex CLI, the IDE extension and the Codex app.
Gemini
The Gemini app, Antigravity, Gemini CLI, Gemini Enterprise with OAuth, and the Gemini API.
Cursor, VS Code & other clients
Cursor, VS Code with GitHub Copilot, Windsurf, Hermes Agent, OpenClaw, Meta Muse, and the two settings any other MCP client needs.
Grok
Add GSC Wizard as a custom connector in Grok, build an SEO analyst Bot, or use it from Grok Build.
Microsoft Copilot
Add the certified GSC Wizard connector in Copilot Studio or Microsoft 365 Copilot, or connect the full MCP server by hand.
n8n & REST API
The GSC Wizard community node for n8n, and the REST API with its OpenAPI spec for your own scripts and workflows.
Working on a shop? The shopping tools reference and the Merchant Center guides for Claude, ChatGPT, Codex and Grok cover the Merchant Center side of the same connection.
Before you start
- A GSC Wizard subscription or the 7-day trial. MCP access is part of every plan, and it stops answering when a trial ends without a subscription.
- Your properties connected in the app at tool.gscwizard.com. Google access is granted there, never in the assistant, and the assistant sees exactly the properties your GSC Wizard account sees. GA4, Bing Webmaster Tools, Yandex Webmaster and Merchant Center are optional connections, also made in the app.
The server address
Every client gets the same address. Keep the /mcp at the end: the bare domain shows the tool catalogue in a browser but does not answer MCP requests.
https://mcp.gscwizard.com/mcpThe server speaks streamable HTTP, so most clients need nothing installed locally: no Node process and no bridge. The exceptions are clients whose config file can only start local programs, such as the Claude Desktop config file, which go through the small mcp-remote bridge instead. Their guides show how.
Signing in: OAuth or an API key
There are two ways for an assistant to prove it acts for you, and which one you use depends on the client, not on what you want to do.
| Sign in (OAuth) | API key | |
|---|---|---|
| Used by | Clients with a connector screen: the Claude app, ChatGPT, the Gemini app, Grok, Gemini Enterprise, Copilot Studio, and Claude Code or Codex when you choose to sign in | Config files and code: Cursor, VS Code, Windsurf, Antigravity, OpenClaw, scripts, CI jobs, n8n and the REST API |
| What you copy | Only the server address. Leave any client ID and secret fields empty: the assistant registers itself with the server | A key that starts with gscw_live_, sent as Authorization: Bearer gscw_live_... |
| Read-only | Untick Also allow … to make changes on the consent screen | Create the key with the Read only scope |
| Undo | Disconnect the connector in the assistant | Revoke the key on the MCP API keys page |
On the sign-in screen, GSC Wizard says which app wants access and which GSC Wizard account you are signed in as. Check that account before you approve: the assistant gets that account’s properties, and if you run several, it is the most common reason an assistant answers about the wrong sites.
ChatGPT cannot send a fixed key to a remote server, so it always signs in, and Gemini Enterprise only accepts OAuth. Microsoft Copilot Studio’s manual setup takes an OAuth client you create on the MCP API keys page; the Copilot guide covers it.
API keys
Keys are for every client that reads its settings from a file, and for anything that runs without a person at a browser.
- In the app, open Account and then MCP API Keys in the left sidebar.
- Create a key, give it a name you will recognise later (one per client or job is easiest to revoke), and pick a scope: Read only, or Read & write.
- Copy the key straight away. It is shown once and stored only as a hash, so it cannot be shown again; create a new one if it is lost.
Keep keys out of source code: every client guide shows where an environment variable or a password prompt can hold it instead. Creating a key needs an active subscription or trial.
What an assistant can change
Most tools only read. The rest change something in your GSC Wizard account or send something to Google, Bing or another search engine, and they only run with write access.
- Read access covers every report and analysis, URL inspection and the Index Tracker history. A read-only key or sign-in is refused by every write tool before the tool runs, so even an assistant that is tricked by text on a web page cannot change anything. Use it for shared agents, client-facing setups and anything that runs unattended.
- Write access adds the tools that act: adding properties, submitting sitemaps, sending URLs to IndexNow, adding URLs to the Index Tracker, creating and editing annotations, content groups, topic clusters, saved filters and shared reports, and queuing a Merchant Center feed audit.
- Every write is recorded in an audit log against your account, and most clients ask you to confirm a tool call that changes something.
Where the numbers come from
- Search Console reads are served from the GSC Wizard data warehouse wherever possible, which keeps the full history of each stored property without the sampling and row caps of the Search Console API. A request the warehouse cannot answer, such as one that needs search appearance, falls back to the live API.
- Search Console data runs about two days behind. Every answer says which source served it and the last day it is settled through, so an assistant can tell you why its totals stop before today.
- Calls are rate-limited per account: 120 a minute and 3,000 an hour over MCP. A throttled call says how many seconds to wait. Agents that loop over every page one by one hit this first; one analysis tool usually answers the same question in a single call.
What you can ask
Ask in plain language. The assistant picks the tools, and naming one only helps when it picks the wrong one.
- “Give me a performance summary for example.com for the last 28 days against the 28 days before.”
- “Which pages lost the most clicks this quarter, and is it rankings or demand?”
- “Where am I cannibalizing my own keywords, and which page should win each one?”
- “Which queries in positions 4 to 20 would bring the most extra clicks if they reached the top three?”
- “Why aren’t my new product pages indexed? Inspect the ten newest URLs in the sitemap.”
- “Did the last Google core update hit us, and which sections?”
The full list of tools, with the arguments each one takes, is on the MCP server page. For the protocol details (transport, OAuth discovery, sessions, pagination) see the Search Console MCP reference, and for what each data source adds, the GSC MCP, GA4 MCP, Bing Webmaster Tools MCP, Yandex Webmaster MCP and Merchant Center MCP pages.
Ready-made skills
The MCP server gives an agent the tools; the skills tell it how to use them. They are guided workflows for a site audit, a traffic drop, content decay, cannibalization, quick wins, a client report and more, written against the real tool names, and each one asks the agent to name the tool and date range behind every figure it reports.
npx skills add jbobbink/seo-gsc-wizard- The command installs the skills into Claude Code, Cursor, Codex and the other agents the skills CLI supports. It installs no MCP server, so add
https://mcp.gscwizard.com/mcpto the agent as well. - In Claude Code, the plugin installs the skills and the server together: see the Claude guide. Hermes Agent has its own plugin with the same skills: see other clients.
- Agents that read
/.well-known/agent-skills/index.jsonfind the same skills on gscwizard.com, sonpx skills add https://www.gscwizard.comworks too. - The source is on GitHub. The skills are free; the tools they call need a GSC Wizard subscription or trial.
Troubleshooting
Each client guide has its own list; these apply to every client.
The tools never appear
Most clients read their MCP settings only at startup, so quit and reopen the app fully (not just the window) after you add the server. Check that the address ends in /mcp.
Every call returns 401
With a key, check that the header is exactly Authorization: Bearer gscw_live_..., that the key is not revoked, and that the subscription or trial is active. With a sign-in, disconnect and connect again.
A tool that changes something returns 403
The connection is read-only. Create a read-and-write key or reconnect with changes allowed, only if the assistant really needs to act; otherwise make the change in the app.
The assistant answers about the wrong properties
It signed in as another GSC Wizard account. Disconnect it, sign in at tool.gscwizard.com as the right account, and connect again.
A property is missing
The assistant only sees properties connected and active in GSC Wizard. Add it in the app, then ask for the list again. Domain properties carry the sc-domain: prefix.
A tool says notConfigured
The data source behind it, such as GA4, Bing or Merchant Center, is not connected for that property. The answer names the reason; the fix is always in the app, not in the assistant.