Google Search Console MCP Server

A minimal MCP server for Google Search Console

Local serverstdioGo

What is the Google Search Console MCP MCP server?

A minimal MCP server for Google Search Console. That is what the google search console mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A Model Context Protocol (MCP) server that gives AI agents direct access to your Google Search Console data.

The tools it exposes

The server publishes 11 tools. What each one is for:

  • siteUrl — string
  • startDate — string
  • endDate — string
  • dimensions — string
  • rowLimit — number
  • searchType — string
  • queryFilter — string
  • pageFilter — string
  • countryFilter — string
  • deviceFilter — string
  • inspectionUrl — string

What it needs from you

Configuration is passed through the environment: GOOGLE_APPLICATION_CREDENTIALS. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Google Search Console MCP's toolset — siteUrl, startDate, endDate and 8 more — is a fair guide to whether it matches your workflow. It is maintained by sarahpark; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Google Search Console MCP.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
siteUrlstring
startDatestring
endDatestring
dimensionsstring
rowLimitnumber
searchTypestring
queryFilterstring
pageFilterstring
countryFilterstring
deviceFilterstring
inspectionUrlstring

How to install the Google Search Console MCP MCP server

{
  "mcpServers": {
    "gsc": {
      "command": "node",
      "args": ["/absolute/path/to/google-search-console-mcp/build/index.js"],
      "env": {
        "GOOGLE_APPLICATION_CREDENTIALS": "/absolute/path/to/service-account-key.json"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
GOOGLE_APPLICATION_CREDENTIALSConfiguration value read at startup.Optional

Example prompts to try

  • Use Google Search Console MCP to siteUrl.
  • Use Google Search Console MCP to startDate.
  • Use Google Search Console MCP to endDate.

Frequently asked questions

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