Self-host the Google Search Console MCP server

The hosted instance runs the code that is on GitHub. Running your own keeps Google tokens on your hardware, and it is the only way to use the three indexing tools.

Two ways to run it

	On your machine (stdio)	As your own remote server
Who connects	You, from your own MCP client	Anyone you allow, each with their own Google account (or one shared token)
Where Google tokens live	Your machine, in `~/.gsc-mcp/`	Your server, encrypted at rest
Indexing tools	Yes, with `GSC_SCOPES=full`	Not in per-user sign-in mode, which is read-only
Runtime	Node 18+	Node 18+; per-user sign-in needs Node 24+

Run it on your machine

Clone and build. It is not on npm yet, so install from source:

git clone https://github.com/kodotpro/gsc-mcp-remote.git && cd gsc-mcp-remote
npm ci && npm run build

Get a Google OAuth client. In Google Cloud Console, enable the Google Search Console API, then go to Credentials → Create credentials → OAuth client ID → Desktop app and download the JSON.
Run the guided setup. It signs you in, checks the connection with a live API call, and writes your Claude config:
```
node dist/index.js setup
```

Restart Claude and ask “list my Search Console properties”. To configure it by hand, or to use a service account instead, see the README. For Claude Code, the Claude Code guide has a one-line claude mcp add-json command.

GSC_SCOPES=readonly requests a single read-only Google permission and is the recommended setting. full adds the write tools: submit_url, submit_batch, submit_sitemap.

Host it for other people

The same server runs as a remote MCP server, which is what gsc.k-o.pro is. Pick an auth mode first:

	`GSC_HTTP_AUTH=oauth`	`GSC_HTTP_AUTH=bearer` (default)
Who connects	Anyone you allow, with their own Google account	Whoever holds the one token
What they see	Their own properties	Everything the server's single credential sees
claude.ai and Desktop connector UI	Yes, added by URL	No
Claude Code	Yes, through the OAuth flow	Yes, with an `Authorization` header
Runtime	Node 24+	Node 18+

The self-hosting documentation covers the rest: Docker deployment, the reverse proxy, turning on per-user sign-in, Google's app verification, backups, the capacity limits and troubleshooting.

Licence and credit

Apache 2.0. The project is a fork of Suganthan's GSC MCP by Suganthan Mohanadasan, and the NOTICE file in the repository records what this fork changed. Issues and pull requests go to github.com/kodotpro/gsc-mcp-remote.

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