Google Search Console · get-mcp-ads — Claude Code MCP server: setup guide
Read-only MCP server with 20 inspection tools for Google Search Console. It tracks organic performance and spots keyword cannibalization across URLs.
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_ACCESS_TOKEN=<GSC_ACCESS_TOKEN> --env GSC_SITE_URL=<GSC_SITE_URL> --transport stdio get-mcp-ads-google-search-console -- npx -y @getmcpads/google-search-console-mcp-serverWhat Google Search Console does
This server connects Search Console reporting directly to stdio-compliant MCP clients. It ships with 20 read-only tools and omits write operations entirely. Instead of simply pulling raw table rows, it computes differences between date windows and spots competing URLs targeting identical queries.
To prevent draining daily quotas during research, URL Inspection calls are capped at 10 URLs per run. Authentication relies on OAuth environment variables: GSC_CLIENT_ID, GSC_CLIENT_SECRET, and either GSC_REFRESH_TOKEN or GSC_ACCESS_TOKEN, along with GSC_SITE_URL.
Execution requires Node.js ^22.23.4, ^24.22.1, or >=26.12.1. Booting the server on earlier Node versions produces a stderr warning because older runtimes miss essential security patches.
What it helps with
- detect keyword cannibalization across competing landing pages
- inspect URL indexation status without exhausting daily API quotas
- compare clicks and impressions across two consecutive date windows
- review registered properties and submitted sitemap files
Example prompts for the agent
- Check if any URLs on our domain cannibalize rankings for the same query
- Compare search impressions and clicks over the last 14 days against the prior period
- Execute
gsc_detect_cannibalizationon the active site property
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_ACCESS_TOKEN=<GSC_ACCESS_TOKEN> --env GSC_SITE_URL=<GSC_SITE_URL> --transport stdio get-mcp-ads-google-search-console -- npx -y @getmcpads/google-search-console-mcp-serverReplace <…> with your own values. 1 more environment variable is in the server README
Platform CLI
codex mcp add get-mcp-ads-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_ACCESS_TOKEN=<GSC_ACCESS_TOKEN> --env GSC_SITE_URL=<GSC_SITE_URL> -- npx -y @getmcpads/google-search-console-mcp-serverReplace <…> with your own values. 1 more environment variable is in the server README
Config file
{
"mcpServers": {
"get-mcp-ads-google-search-console": {
"command": "npx",
"args": [
"-y",
"@getmcpads/google-search-console-mcp-server"
],
"env": {
"GSC_CLIENT_ID": "<GSC_CLIENT_ID>",
"GSC_CLIENT_SECRET": "<GSC_CLIENT_SECRET>",
"GSC_REFRESH_TOKEN": "<GSC_REFRESH_TOKEN>",
"GSC_ACCESS_TOKEN": "<GSC_ACCESS_TOKEN>",
"GSC_SITE_URL": "<GSC_SITE_URL>"
}
}
}
}Replace <…> with your own values. 1 more environment variable is in the server README
Config file
{
"servers": {
"get-mcp-ads-google-search-console": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@getmcpads/google-search-console-mcp-server"
],
"env": {
"GSC_CLIENT_ID": "<GSC_CLIENT_ID>",
"GSC_CLIENT_SECRET": "<GSC_CLIENT_SECRET>",
"GSC_REFRESH_TOKEN": "<GSC_REFRESH_TOKEN>",
"GSC_ACCESS_TOKEN": "<GSC_ACCESS_TOKEN>",
"GSC_SITE_URL": "<GSC_SITE_URL>"
}
}
}
}Replace <…> with your own values. 1 more environment variable is in the server README
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_ACCESS_TOKEN=<GSC_ACCESS_TOKEN> -e GSC_SITE_URL=<GSC_SITE_URL> get-mcp-ads-google-search-console npx -y @getmcpads/google-search-console-mcp-serverReplace <…> with your own values. 1 more environment variable is in the server README
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_ACCESS_TOKEN=<GSC_ACCESS_TOKEN> --env GSC_SITE_URL=<GSC_SITE_URL> --transport stdio get-mcp-ads-google-search-console -- npx -y @getmcpads/google-search-console-mcp-server`. Replace placeholder values with your Google API credentials.
Can this MCP server modify properties or submit files in Search Console?
No. The server includes 20 read tools and zero write tools by design, so mutating properties or submitting files is not possible.
Which Node.js versions are required?
You need Node.js ^22.23.4, ^24.22.1, or >=26.12.1. Starting on older runtimes prints a stderr warning because older builds lack October 2026 security fixes.
Similar MCP servers
All MCP servers for SEO and GEO →Google Search Console by other authors comes first.
