GSC MCP Guide / Search Console MCP in Cursor and Claude Code

Search Console MCP in Cursor and Claude Code

Updated November 2026

Short answer

In Claude Code, register a hosted server with one command (claude mcp add --transport http, a name and the URL), then sign in with /mcp. In Cursor, add the URL to ~/.cursor/mcp.json and switch it on in Cursor Settings > MCP. The payoff is that the agent reads your Search Console data and edits your site's code in the same session.

Why connect Search Console to a coding agent

In a chat app, the assistant finds the problem and you fix it. Cursor and Claude Code have your codebase, so one session can go from “which pages are stuck on page 2?” to a diff that fixes their titles and content.

Any Search Console server will tell the agent which pages to work on. A server with SERP data, such as LinkGPT, can also show it what the pages ranking above yours cover, so the edit closes a real gap instead of guessing at one.

Claude Code

Register a hosted server once, at user scope, so it works in every project and never lands in the repo:

claude mcp add --transport http --scope user search-console https://mcpsearchconsole.com/mcp

Start Claude Code, type /mcp, pick the server and sign in. claude mcp list shows whether it’s connected.

Swap the URL for any other hosted server:

Server URL
LinkGPT https://www.linkgpt.app/mcp
SearchConsole.ai https://searchconsole.ai/mcp
GSC Wizard https://mcp.gscwizard.com/mcp

Cursor

Add the server to ~/.cursor/mcp.json, your user-level config, so it stays out of the repo:

{
  "mcpServers": {
    "search-console": {
      "url": "https://mcpsearchconsole.com/mcp"
    }
  }
}

Then open Cursor Settings > MCP and switch it on. Servers that use OAuth ask you to sign in the first time. If a server gives you a private link instead, paste that as the url and treat the file like a password.

For the open-source mcp-gsc, search for mcp-search-console in the Cursor Marketplace. It still needs the Google Cloud credentials from the mcp-gsc setup guide.

Codex CLI

Codex reads MCP servers from ~/.codex/config.toml. mcp-gsc’s README has the block to paste, and SearchConsole.ai lists Codex steps for its hosted server.

A prompt that uses both

Find the three pages closest to page 1 in Search Console. For each, compare our page with the top three results for its main query, then edit the page in this repo to cover what’s missing. Show me the diff before committing.

The first step works with any Search Console server. The comparison step needs one that can read live search results.

For chat apps, see the setup for Claude and ChatGPT, or compare every option in the Google Search Console MCP server list.

Common questions

Why connect Search Console to a coding tool and not just Claude?

Because the coding tool has your repo. A chat assistant can tell you which title to rewrite. Cursor or Claude Code can rewrite it in the file and show you the diff.

Is it safe to put the MCP URL in my repo?

A plain server URL is fine, because you sign in separately and nothing secret is in it. A private link is different: it works like a password, so keep it in your user-level config, not in a project file you commit.

Does mcp-gsc work in Cursor?

Yes. It's in the Cursor Marketplace as mcp-search-console, or you can add it to ~/.cursor/mcp.json by hand. You still need the Google Cloud credentials from its setup.