Google Search Console MCP Server

What this does

Google Search Console exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

GSC_SERVICE_ACCOUNT_KEY
GSC_SERVICE_ACCOUNT_KEY_FILE
GSC_CLIENT_ID
GSC_CLIENT_SECRET
GSC_REFRESH_TOKEN
GOOGLE_APPLICATION_CREDENTIALS
GSC_SITE_URL
GSC_ALLOWED_SITES
GSC_READ_ONLY
GSC_ALLOW_TOOLS
GSC_DENY_TOOLS

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Google Search Console?

Run the Claude Code command in the install section to add Google Search Console to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Google Search Console?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Google Search Console as well.

Does Google Search Console need an API key?

Yes. Before it can run, set these environment variables: GSC_SERVICE_ACCOUNT_KEY, GSC_SERVICE_ACCOUNT_KEY_FILE, GSC_CLIENT_ID, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN, GOOGLE_APPLICATION_CREDENTIALS, GSC_SITE_URL, GSC_ALLOWED_SITES, GSC_READ_ONLY, GSC_ALLOW_TOOLS, GSC_DENY_TOOLS. They go in the env block of your MCP config.