Use Google Search Console in Claude Code

Claude Code connects to the hosted server over HTTP. One command adds it, and Claude Code runs the Google sign-in through its own OAuth flow.

Add the server

claude mcp add --transport http gsc https://gsc.k-o.pro/mcp

gsc is the name Claude Code shows for the server; any name works. Claude Code's MCP documentation covers the command in full.

Choose a scope

Claude Code stores the server in one of three scopes. Local is the default.

Scope	Where it loads	Add it with
Local	This project only, private to you	`claude mcp add --transport http gsc https://gsc.k-o.pro/mcp`
User	All your projects	`claude mcp add --transport http --scope user gsc https://gsc.k-o.pro/mcp`
Project	Everyone working in the repository, via `.mcp.json`	`claude mcp add --transport http --scope project gsc https://gsc.k-o.pro/mcp`

A project-scoped entry shares the address, not an account: each teammate still signs in with their own Google account and sees only their own properties.

Sign in

Inside Claude Code, run /mcp, pick the server, and follow the steps in your browser. You see this server's consent page first, naming the application and the address the result goes to, then Google's sign-in asking for read-only Search Console access. If the browser does not open on its own, copy the URL Claude Code prints and open it yourself.

Then ask: “List my Search Console properties.”

Questions that suit a terminal

“Inspect the five URLs we shipped today and tell me which are not indexed yet.” (inspect_url)
“Do /pricing and /pricing/ both get impressions for the same queries?” (cannibalization_check)
“Check the click numbers in this README against live data before I commit it.” (verify_claim)
“Write a 28-day performance report for sc-domain:example.com.” (generate_report; on this hosted instance the report comes back in the conversation)

Manage it

claude mcp list
claude mcp get gsc
claude mcp remove gsc

Removing the server deletes the OAuth tokens Claude Code stored for it. To erase what this server stores about you as well, ask Claude to run disconnect_account first.

Run it locally instead

If you would rather your Google token stayed on your machine, build the server from source and add it over stdio. You need your own Google OAuth client; the self-hosting guide covers getting one. Then:

claude mcp add-json gsc '{"command":"node","args":["/absolute/path/to/gsc-mcp-remote/dist/index.js"],"env":{"GSC_AUTH_MODE":"oauth","GSC_OAUTH_SECRETS_FILE":"/absolute/path/to/client_secret.json","GSC_SCOPES":"readonly"}}'

Local mode is also the only way to use the three indexing tools, which need GSC_SCOPES=full.

About this page

Built and run by Oleksii Khoroshun, an SEO with nine years in the field who builds tools at k-o.pro. It is a fork of Suganthan's GSC MCP by Suganthan Mohanadasan: the analysis logic and most of the tool set are his design, and this fork adds multi-property access, the remote server and per-user sign-in.

Version 3.8.0 · page updated 13 October 2026 · changelog