Google Search Console MCP Server

A Model Context Protocol (MCP) server providing access to Google Search Console.

Local serverstdioGo

What is the Google Search Console MCP server?

If you want an AI assistant working directly with Google Search Console, the google search console mcp server is the bridge. A Model Context Protocol (MCP) server providing access to Google Search Console.

What Google Search Console does

A Model Context Protocol (MCP) server providing comprehensive access to Google Search Console data with enhanced analytics capabilities.

Key capabilities

  • Enhanced Search Analytics — Retrieve up to 25,000 rows of performance data
  • Advanced Filtering — Support for regex patterns and multiple filter operators
  • Quick Wins Detection — Automatically identify optimization opportunities
  • Rich Dimensions — Query, page, country, device, and search appearance analysis
  • Flexible Date Ranges — Customizable reporting periods with historical data access

Tools it exposes

Once connected, the assistant can call this tool directly:

  • search_analytics — Get comprehensive search performance data from Google Search Console with enhanced analytics capabilities

Installing the google search console mcp server

The server is distributed via npm as mcp-server-gsc, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

The server reads one environment variable: GOOGLE_APPLICATION_CREDENTIALS. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

  • Node.js 18 or later - Google Cloud Project with Search Console API enabled - Service Account credentials with Search Console access

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Google Search Console sits in that group, and the shape of its toolset — search_analytics — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • Written in Go.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the google search console mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
search_analyticsGet comprehensive search performance data from Google Search Console with enhanced analytics capabilities.

How to install the Google Search Console MCP server

{
  "mcpServers": {
    "server-gsc": {
      "command": "npx",
      "args": ["-y", "mcp-server-gsc"],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js 18 or later - Google Cloud Project with Search Console API enabled - Service Account credentials with Search Console access
VariableDescriptionRequired
GOOGLE_APPLICATION_CREDENTIALSConfiguration value read at startup.Optional

Example prompts to try

  • Use Google Search Console to search analytics.

Frequently asked questions

It connects Google Search Console to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (search_analytics) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Google Search Console directly.