Google Search Console · acamolese — Claude Code MCP server: setup
This MCP server reads Google Search Console data, checks indexing, and builds SEO audits. Use it for recurring reviews and traffic issue analysis.
claude mcp add --env GSC_CLIENT_ID=<GSC_CLIENT_ID> --env GSC_CLIENT_SECRET=<GSC_CLIENT_SECRET> --env GSC_REFRESH_TOKEN=<GSC_REFRESH_TOKEN> --env GSC_SERVICE_ACCOUNT_FILE=<GSC_SERVICE_ACCOUNT_FILE> --env GSC_REPORT_LANGUAGE=<GSC_REPORT_LANGUAGE> --transport stdio google-search-console -- uvx mcp-google-search-consoleWhat Google Search Console does
The server connects an MCP client to Google Search Console and exposes tools for Search Analytics queries, URL inspection, indexing checks, and sitemap review. It can also surface query cannibalization, click losses, weak CTR, and pages that are steadily declining.
Built-in workflows cover a weekly report, an indexing audit, and content opportunity analysis. A full audit can be rendered as an HTML report with custom branding and English or Italian output. Access is read-only, so the server cannot change a property or its sitemaps.
Running it through uvx requires Google Search Console credentials. OAuth, a service account, or Application Default Credentials can provide access. The Google Search Console API must be enabled for the OAuth setup.
What it helps with
- check which URLs are indexed
- spot queries shared by competing pages
- compare search performance across periods
- produce a branded HTML audit
- find sitemap errors and warnings
Example prompts for the agent
- Use
gsc_traffic_dropsto inspect lost clicks and explain the likely causes. - Run
gsc_indexing_issuesfor these URLs and group the indexing problems. - Create a weekly Google Search Console review with
gsc_weekly_report.
How to install Google Search Console
Platform CLI
claude mcp add --env GSC_CLIENT_ID=<GSC_CLIENT_ID> --env GSC_CLIENT_SECRET=<GSC_CLIENT_SECRET> --env GSC_REFRESH_TOKEN=<GSC_REFRESH_TOKEN> --env GSC_SERVICE_ACCOUNT_FILE=<GSC_SERVICE_ACCOUNT_FILE> --env GSC_REPORT_LANGUAGE=<GSC_REPORT_LANGUAGE> --transport stdio google-search-console -- uvx mcp-google-search-consoleReplace <…> with your own values. 1 more environment variable is in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from mcp-google-search-console <command>
Platform CLI
codex mcp add google-search-console --env GSC_CLIENT_ID=<GSC_CLIENT_ID> --env GSC_CLIENT_SECRET=<GSC_CLIENT_SECRET> --env GSC_REFRESH_TOKEN=<GSC_REFRESH_TOKEN> --env GSC_SERVICE_ACCOUNT_FILE=<GSC_SERVICE_ACCOUNT_FILE> --env GSC_REPORT_LANGUAGE=<GSC_REPORT_LANGUAGE> -- uvx mcp-google-search-consoleReplace <…> with your own values. 1 more environment variable is in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from mcp-google-search-console <command>
Config file
{
"mcpServers": {
"google-search-console": {
"command": "uvx",
"args": [
"mcp-google-search-console"
],
"env": {
"GSC_CLIENT_ID": "<GSC_CLIENT_ID>",
"GSC_CLIENT_SECRET": "<GSC_CLIENT_SECRET>",
"GSC_REFRESH_TOKEN": "<GSC_REFRESH_TOKEN>",
"GSC_SERVICE_ACCOUNT_FILE": "<GSC_SERVICE_ACCOUNT_FILE>",
"GSC_REPORT_LANGUAGE": "<GSC_REPORT_LANGUAGE>"
}
}
}
}Replace <…> with your own values. 1 more environment variable is in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from mcp-google-search-console <command>
Config file
{
"servers": {
"google-search-console": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-google-search-console"
],
"env": {
"GSC_CLIENT_ID": "<GSC_CLIENT_ID>",
"GSC_CLIENT_SECRET": "<GSC_CLIENT_SECRET>",
"GSC_REFRESH_TOKEN": "<GSC_REFRESH_TOKEN>",
"GSC_SERVICE_ACCOUNT_FILE": "<GSC_SERVICE_ACCOUNT_FILE>",
"GSC_REPORT_LANGUAGE": "<GSC_REPORT_LANGUAGE>"
}
}
}
}Replace <…> with your own values. 1 more environment variable is in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from mcp-google-search-console <command>
Platform CLI
gemini mcp add -e GSC_CLIENT_ID=<GSC_CLIENT_ID> -e GSC_CLIENT_SECRET=<GSC_CLIENT_SECRET> -e GSC_REFRESH_TOKEN=<GSC_REFRESH_TOKEN> -e GSC_SERVICE_ACCOUNT_FILE=<GSC_SERVICE_ACCOUNT_FILE> -e GSC_REPORT_LANGUAGE=<GSC_REPORT_LANGUAGE> google-search-console uvx mcp-google-search-consoleReplace <…> with your own values. 1 more environment variable is in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from mcp-google-search-console <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Google Search Console
How do I install Google Search Console in Claude Code?
Run `claude mcp add --env GSC_CLIENT_ID=<GSC_CLIENT_ID> --env GSC_CLIENT_SECRET=<GSC_CLIENT_SECRET> --env GSC_REFRESH_TOKEN=<GSC_REFRESH_TOKEN> --env GSC_SERVICE_ACCOUNT_FILE=<GSC_SERVICE_ACCOUNT_FILE> --env GSC_REPORT_LANGUAGE=<GSC_REPORT_LANGUAGE> --transport stdio google-search-console -- uvx mcp-google-search-console`.
What does Google Search Console do?
This MCP server gives an agent read access to Search Console for query analysis, indexing checks, traffic diagnosis, and HTML audit generation. It cannot modify properties or sitemaps.
What is required before the server can run?
Provide Google authentication through OAuth, a service account, or Application Default Credentials. OAuth setup also requires the Google Search Console API and access to the property.
Similar MCP servers
Everything for SEO and GEO →Google Search Console by other authors comes first.
