GSC Search Insights

Explore Google Search Console and Bing Webmaster Tools reports, compare search performance, and find SEO opportunities. Hosted remote MCP server (https://api.gscmcpserver.com/mcp) with OAuth and 12 read-only tools.

Hosted MCP Server

npx add-mcp 'https://api.gscmcpserver.com/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

Before you start

You need three things: access to at least one verified property in Google Search Console or Bing Webmaster Tools, an AI app that supports remote MCP servers, and a GSC MCP Server account to sit between them.

  • Search Console access. Any permission level works for reading data. If you can open the Performance report for a property, the server can read it on your behalf.
  • An MCP-capable client. Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex, Antigravity CLI, Devin Desktop (formerly Windsurf) and Cline all qualify. Business and enterprise workspaces sometimes need an administrator to allow custom connectors or plugins.
  • Your server endpoint. After signing in, the Client setup page in your dashboard shows your MCP URL and the exact configuration for each client.

New to the idea? Read what a Search Console MCP server is first. It explains the moving parts in plain English. Still choosing? Compare Search Console MCP servers before you sign up.

Step 1: Connect Google and Bing

  1. Sign in with Google or GitHub.
  2. Open Data sources and choose Connect Google or Connect Bing.
  3. Approve the read-only consent screen. You will be returned to the dashboard with your properties listed.
  4. Give the connection a label you will recognise in conversation, such as “Client – Acme” or “Personal blog”. Labels make it easier to tell the assistant which site you mean.

You can test the connection immediately in the dashboard Playground, which runs the same tools your assistant will use, before you set up any client.

Claude (web and desktop)

Claude supports remote MCP servers as custom connectors, and it signs in through OAuth so you do not paste any key.

  1. In Claude, open Customize → Connectors, select +, then Add custom connector.
  2. Name it gscmcpserver and paste your MCP URL from the dashboard.
  3. Complete the sign-in prompt and choose Allow for read access.
  4. In a new chat, enable the connector from the tools menu and ask your first question.

On Team and Enterprise, an Owner adds it under Organization settings → Connectors; members then connect from Customize → Connectors. Free plans allow one custom connector. Anthropic’s custom connectors guide has the full steps.

[!note] Note Why localhost fails in Claude Claude connects to MCP servers from Anthropic’s cloud, even in the desktop app. A server running on your own machine is unreachable, so use the hosted endpoint or a public HTTPS deployment.

ChatGPT

ChatGPT on the web adds remote MCP servers as plugins, using OAuth with dynamic client registration. OpenAI’s guide to connecting an MCP server to ChatGPT shows the same flow.

  1. Go to chatgpt.com/plugins, select +, then Add custom MCP server. If the option is missing, your workspace administrator may need to enable it.
  2. Enter gscmcpserver as the name, paste your public HTTPS MCP URL, and select OAuth. Leave discovery on; the read-only scope is search:read.
  3. Accept the warning, select Create as a plugin and install it.
  4. Sign in to your GSC MCP Server account and choose Allow read access.
  5. Add the plugin to a conversation and ask about your search performance.

You can revoke ChatGPT’s access at any time from Connected AI clients on the setup page without affecting other assistants.

Cursor

Cursor reads MCP servers from a JSON file. Use .cursor/mcp.json for one project or ~/.cursor/mcp.json for every project, as described in Cursor’s MCP documentation.

  1. Add a gscmcpserver entry to the mcpServers object with your endpoint as url. The setup page generates this snippet for you.
  2. Open Cursor’s MCP settings, sign in when prompted, check the server is green, and enable its tools for the agent.
  3. Prefer a key? Create one on the dashboard setup page and send it as an Authorization: Bearer header. Treat it like a password and never commit it to a repository.

Developers get the most from Cursor when the search data sits next to the code that produces the pages. Our technical SEO in Cursor and VS Code guide covers that workflow.

VS Code with GitHub Copilot

VS Code adds remote servers through a guided flow; its MCP server documentation covers every configuration option.

  1. Open the Command Palette and run MCP: Add Server.
  2. Choose HTTP, paste your endpoint and name it gscmcpserver.
  3. Save it to your user settings or to the workspace’s .mcp.json.
  4. Run MCP: List Servers to start it, sign in when VS Code asks (or add your API key as an Authorization: Bearer header), and enable the tools in Copilot Chat’s tool picker.

Claude Code, Codex and Antigravity CLI

Terminal agents register remote servers with a single command or a short config entry. Your dashboard generates both with your endpoint filled in. The shape is:

  • Claude Code: claude mcp add --transport http --scope user gscmcpserver <url>, then run /mcp and choose Authenticate to sign in.
  • Codex: codex mcp add gscmcpserver --url <url>, then codex mcp login gscmcpserver.
  • Antigravity CLI (which replaced Gemini CLI for most individual users in June 2026): add a gscmcpserver entry with your endpoint as serverUrl to ~/.gemini/config/mcp_config.json, then type /mcp. Antigravity runs the sign-in for you.

Each one signs in through OAuth in your browser. For runs that cannot open a browser, such as claude -p or a CI job, send your API key as an Authorization: Bearer header instead. Devin Desktop (formerly Windsurf) and Cline follow the same pattern through their MCP configuration files; Gemini CLI still works with paid Gemini API keys via gemini mcp add --transport http. The official MCP pages for Claude Code, Codex and Antigravity list every option. Once Claude Code is connected, our guide to Claude Code for SEO shows three workflows that run inside a repo.

Your first five prompts

Run these in order. They confirm the connection works and give you a useful snapshot of the site within a few minutes.

Try this prompt

List my connected search properties and tell me which account each one belongs to.

Try this prompt

Give me a search overview for the last 28 days: clicks, impressions, CTR and average position, plus the change from the previous 28 days.

Try this prompt

What are my top 20 queries and top 20 landing pages by clicks this month? Flag anything that dropped more than 20%.

Try this prompt

Find striking distance opportunities: queries at positions 8–20 with meaningful impressions. Which three pages should I improve first?

Try this prompt

Check my sitemaps in Google and Bing: status, errors and warnings, how many URLs each lists, and when each was last downloaded.

Prompt four is the start of a bigger workflow. Our striking distance keywords guide turns it into a repeatable process, and our list of Search Console prompts for Claude and ChatGPT has more to try next.

Troubleshooting

SymptomLikely causeFix
“Couldn’t reach server” in Claude or ChatGPTLocalhost or plain HTTP URLUse the public HTTPS endpoint from the dashboard
401 Unauthorized in an editorSign-in not completed, or a mistyped bearer headerRun the client’s sign-in again, or re-copy the API key; the header must read Authorization: Bearer <key>
Tools load but return no propertiesNo Google or Bing account connected, or it is disabledConnect or re-enable it under Data sources
A property is missingThe signed-in Google account lacks access to itAdd that account as a user in Search Console, then reconnect
“Usage limit reached”Monthly tool-call allowance used upWait for the reset or upgrade on the pricing section
Custom connector or plugin option missingWorkspace policyAsk your workspace administrator to allow it

Running an agency? Once the connection works, the AI client reporting workflow shows how to use multiple client accounts in one conversation.

Frequently asked questions

Can I connect Google Search Console to ChatGPT for free?

Yes. The GSC MCP Server free plan connects one Google or Bing account and includes 30 tool calls a month. Your ChatGPT plan and workspace settings decide whether custom MCP plugins are available to you.

Why does ChatGPT or Claude reject my localhost URL?

Claude and ChatGPT connect from their own cloud, so they cannot reach a server running on your laptop. Use the hosted endpoint from your dashboard, which is already public HTTPS. If you are testing a server of your own, expose it through a tunnel.

Do I need an API key?

Usually not. Claude, ChatGPT, Claude Code, Codex, Cursor and most other clients sign in through OAuth in your browser. An API key, created on the setup page of your dashboard and sent as an Authorization: Bearer header, is for clients and scripts that cannot complete a browser sign-in, such as claude -p or a CI job.

Can I connect several Search Console accounts?

Yes. Each Google or Bing account you connect counts as one connection, and every verified property inside it becomes available. The Pro plan supports 5 accounts and the Agency plan supports 20.

Is my data used to train AI models?

GSC MCP Server does not train models on your data. Whether your AI provider uses conversation content for training depends on that provider’s settings and your plan, so check their data controls.