GitHub - AkashRajpurohit/gsc-mcp: 🔍 An MCP server that gives your AI assistant read-only access to your Google Search Console data.

Ask your assistant things like "what are my top queries this month?" or "is this page indexed yet?", and it pulls the numbers straight from the Search Console API. No opening the dashboard, no fiddling with date ranges.

The server runs on your own machine and only ever reads. It uses Google's read-only scope, so your assistant can see your data but cannot change anything in your account. One service-account key covers every property you own.

What you can ask

• "List all my Search Console properties."
• "What are my top 20 queries for example.com in the last 28 days?"
• "Which queries get lots of impressions but a low CTR?"
• "Show me the top pages for example.com on mobile."
• "Which pages lost the most clicks this month compared to last month?"
• "Is https://example.com/blog/my-post/ indexed by Google?"
• "How many URLs did my sitemap submit versus get indexed?"

Setup

You need Node.js 22.5 or newer and a Google service-account key that can read your properties. Three steps: create a key, grant it access, add the server to your client.

1. Create a service-account key

Create a service account in any Google Cloud project, save its JSON key to ~/.config/gsc-mcp/key.json, and enable the Search Console API. The Cloud project you pick does not matter; the key works for any property you grant it on.

gcloud config set project YOUR_PROJECT_ID
gcloud services enable searchconsole.googleapis.com
gcloud iam service-accounts create gsc-reader --display-name="GSC Reader"

mkdir -p ~/.config/gsc-mcp
gcloud iam service-accounts keys create ~/.config/gsc-mcp/key.json \
  --iam-account=gsc-reader@YOUR_PROJECT_ID.iam.gserviceaccount.com

2. Grant it access to each property

In Search Console, open each property, go to Settings → Users and permissions → Add user, and add the service account's email (gsc-reader@YOUR_PROJECT_ID.iam.gserviceaccount.com) with the Restricted (read) role. Adding a new site later is just one more grant here.

3. Add gsc-mcp to your client

Claude Code:

claude mcp add gsc --scope user -- npx -y @akashrajpurohit/gsc-mcp

{
  "mcpServers": {
    "gsc": {
      "command": "npx",
      "args": ["-y", "@akashrajpurohit/gsc-mcp"]
    }
  }
}

If your key is not at the default path, add "env": { "GSC_KEY_PATH": "/path/to/key.json" } to the entry (or set it in your shell for the CLI).

4. Check it works

npx @akashrajpurohit/gsc-mcp doctor

This checks your Node version, credentials, Google authentication, and how many properties you can read. If everything is green, start a new session in your client and ask it to list your Search Console sites.

Tools

Data comes straight from Search Console, so you see the same window Google shows everyone (about 16 months of history, with its usual sampling).

{
  "siteUrl": "sc-domain:example.com",
  "startDate": "2026-06-01",
  "endDate": "2026-06-30",
  "dimensions": ["query", "page"],
  "filters": [
    { "dimension": "country", "operator": "equals", "expression": "ind" }
  ],
  "searchType": "web",
  "rowLimit": 5000
}

{
  "siteUrl": "sc-domain:example.com",
  "period": { "startDate": "2026-06-01", "endDate": "2026-06-30" },
  "dimensions": ["query", "page"],
  "rowCount": 842,
  "hasMore": false,
  "rows": [],
  "warnings": []
}

{
  "current": { "startDate": "2026-06-01", "endDate": "2026-06-30" },
  "previous": { "startDate": "2026-05-02", "endDate": "2026-05-31" },
  "summary": {
    "clicks": { "current": 1840, "previous": 2160, "change": -320, "changePercent": -14.81 }
  },
  "groupBy": "page",
  "largestDeclines": [
    {
      "page": "https://example.com/docs",
      "currentClicks": 210,
      "previousClicks": 390,
      "change": -180,
      "changePercent": -46.15
    }
  ],
  "largestGains": []
}

{
  "siteUrl": "sc-domain:example.com",
  "type": "striking_distance",
  "datePreset": "last_28_days",
  "minImpressions": 200,
  "limit": 5
}

{
  "type": "striking_distance",
  "dimension": "query",
  "criteria": { "minPosition": 11, "maxPosition": 20, "minImpressions": 200 },
  "count": 4,
  "opportunities": [
    { "query": "immich photo alternative", "clicks": 0, "impressions": 1620, "ctr": 0, "position": 17.7 }
  ]
}

Command line

The gsc-mcp command works on its own too, handy for a quick check without a client:

npx @akashrajpurohit/gsc-mcp sites
npx @akashrajpurohit/gsc-mcp queries "sc-domain:example.com"
npx @akashrajpurohit/gsc-mcp inspect "sc-domain:example.com" "https://example.com/blog/my-post/"

Run gsc-mcp --help for the full list. Domain properties look like sc-domain:example.com; URL-prefix properties look like https://example.com/.

Configuration

Stability

As of 1.0.0 the tool names and their input and output shapes are stable and follow semantic versioning. Breaking changes to a tool's inputs or outputs will only land in a future major release. New optional inputs and additive fields may arrive in minor releases. The server stays read-only.

Security & privacy

The server is read-only, runs locally, and collects no telemetry. Your key is read from disk and sent only to Google, never anywhere else, and errors are sanitized so key material never lands in logs or transcripts. Full details and how to report a vulnerability are in SECURITY.md.

Troubleshooting

Run npx @akashrajpurohit/gsc-mcp doctor first, since it catches most problems. When a tool call fails, the error also carries a short hint on how to fix it. Common ones:

• sites returns an empty list: the service account is not granted on any property yet. The email you added in Search Console must match the key's client_email exactly.
• Auth or "file not found" errors: the key is not where the server expects it. Check the path or set GSC_KEY_PATH.
• One property returns 403: that property has not been shared with the service account. Add it under Users and permissions.
• "Search Console API is disabled": enable it with gcloud services enable searchconsole.googleapis.com.

Contributing

Contributions are welcome. The project is small and has no build step. See CONTRIBUTING.md for the full guide and ROADMAP.md for what is and is not planned.

git clone https://github.com/AkashRajpurohit/gsc-mcp.git
cd gsc-mcp
npm install
npm test

Tests use Node's built-in runner and are fully offline: no network and no real credentials needed. CI runs them on every push and pull request.

License

MIT. See LICENSE.

This project is not affiliated with, endorsed by, or associated with Google. It is an independent tool that talks to Google's public Search Console API using credentials you create and control. "Google Search Console" is a trademark of Google LLC, used here only to describe what the tool works with. The tool is provided as-is, with no warranty.