Google Search Console MCP

What this does

Google Search Console MCP 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:

GOOGLE_SEARCH_CONSOLE_CLIENT_ID
GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET
GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN
GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN
GOOGLE_SEARCH_CONSOLE_OAUTH_PORT
GOOGLE_SEARCH_CONSOLE_API_BASE
GOOGLE_SEARCH_CONSOLE_TIMEOUT_MS
GOOGLE_SEARCH_CONSOLE_MAX_RETRIES

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

How do I install Google Search Console MCP?

Run the Claude Code command in the install section to add Google Search Console MCP 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 MCP?

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 MCP as well.

Does Google Search Console MCP need an API key?

Yes. Before it can run, set these environment variables: GOOGLE_SEARCH_CONSOLE_CLIENT_ID, GOOGLE_SEARCH_CONSOLE_CLIENT_SECRET, GOOGLE_SEARCH_CONSOLE_REFRESH_TOKEN, GOOGLE_SEARCH_CONSOLE_ACCESS_TOKEN, GOOGLE_SEARCH_CONSOLE_OAUTH_PORT, GOOGLE_SEARCH_CONSOLE_API_BASE, GOOGLE_SEARCH_CONSOLE_TIMEOUT_MS, GOOGLE_SEARCH_CONSOLE_MAX_RETRIES. They go in the env block of your MCP config.