# google-search-console

Gives your agent read-only access to Search Console: queries, impressions, clicks, indexing status and sitemaps. Handy when you want to dig through search traffic inside the chat.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 9
- Author: sarahpark
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/sarahpark/google-search-console-mcp
- Updated: 2026-09-19
- HTML: https://affpapa.org/en/nevibecode/mcp/sarahpark-google-search-console

## What it does

The server runs on your machine and talks to Google Search Console through its API. Your agent can see which properties you own, pull search statistics and check whether a page is indexed. It cannot edit your site or touch Search Console settings. The toolset starts with `list_sites`, which enumerates the properties you can reach, and `search_analytics`, which returns clicks, impressions, CTR and position.

You need a Google Cloud project with the Search Console API turned on, Node.js with npm, and an MCP client. The simplest path is signing in as yourself with Application Default Credentials: your existing Search Console permissions apply, so no extra user has to be added to each property. Install the Google Cloud CLI, run `gcloud auth application-default login` with the `webmasters.readonly` scope, then `gcloud auth application-default set-quota-project YOUR_PROJECT_ID`. Skip that last command and requests fail — the quota project is mandatory.

A service account key works too. Keep the file outside your repo and point `GOOGLE_APPLICATION_CREDENTIALS` at its absolute path. The server reads that variable before falling back to local ADC, so if you later switch to signing in as yourself, drop the old key path from your client config and environment. In Claude, `claude mcp add gsc --scope user -- npx -y @sarahpark/google-search-console-mcp@1.1.0` makes the server available across all your projects.

## Requirements
- Needs: Node.js (commands run via npx)
- Environment variables: `GOOGLE_APPLICATION_CREDENTIALS` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add google-search-console -e GOOGLE_APPLICATION_CREDENTIALS=<GOOGLE_APPLICATION_CREDENTIALS> -- npx -y @sarahpark/google-search-console-mcp
```
Replace <…> with your own values

### Codex

**Platform CLI**
```bash
codex mcp add sarahpark-google-search-console --env GOOGLE_APPLICATION_CREDENTIALS=<GOOGLE_APPLICATION_CREDENTIALS> -- npx -y @sarahpark/google-search-console-mcp
```
Replace <…> with your own values

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "sarahpark-google-search-console": {
            "command": "npx",
            "args": [
                "-y",
                "@sarahpark/google-search-console-mcp"
            ],
            "env": {
                "GOOGLE_APPLICATION_CREDENTIALS": "<GOOGLE_APPLICATION_CREDENTIALS>"
            }
        }
    }
}
```
Replace <…> with your own values

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "sarahpark-google-search-console": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@sarahpark/google-search-console-mcp"
            ],
            "env": {
                "GOOGLE_APPLICATION_CREDENTIALS": "<GOOGLE_APPLICATION_CREDENTIALS>"
            }
        }
    }
}
```
Replace <…> with your own values

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add -e GOOGLE_APPLICATION_CREDENTIALS=<GOOGLE_APPLICATION_CREDENTIALS> sarahpark-google-search-console npx -y @sarahpark/google-search-console-mcp
```
Replace <…> with your own values

## When to use it
- spot queries with high impressions and low CTR
- compare mobile and desktop search performance
- check whether a specific URL is indexed
- list the Search Console properties you can access
- review sitemap status

## Example prompts
- Use the `gsc` server to list my Search Console properties.
- Check the indexing status of `https://example.com/blog/my-post`.

## Similar
- [New-Term Radar](https://affpapa.org/en/nevibecode/mcp/new-term-radar.md) — MCP server · ★ 1766
- [NotFair](https://affpapa.org/en/nevibecode/mcp/notfair.md) — MCP server · ★ 4055
- [seo-monster](https://affpapa.org/en/nevibecode/mcp/seo-monster.md) — MCP server · ★ 553
- [Google Maps MCP Server](https://affpapa.org/en/nevibecode/mcp/google-maps-mcp-server.md) — MCP server · ★ 479
- [Search Console MCP](https://affpapa.org/en/nevibecode/mcp/search-console-mcp.md) — MCP server · ★ 308
- [squirrelscan](https://affpapa.org/en/nevibecode/mcp/squirrelscan.md) — MCP server · ★ 296

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md