Google Search Console MCP Server for Node.js - connect GSC data to Claude, Cursor and other MCP clients
Connect Google to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Google Search Console MCP Server for Node.js - connect GSC data to Claude, Cursor and other MCP clients. The google mcp server is what makes that connection.
A powerful Model Context Protocol (MCP) server that connects Google Search Console data to AI assistants like Claude, Cursor, and other MCP-compatible clients. Get instant access to your website's search performance, keywords, rankings, and more through natural language queries.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Installation — The Installation tool exposed by this serverPrerequisites — 1. Google Search Console property with verified ownership 2. Google Cloud Project with Search Console API enabled 3. **Service accountDimensions — The Dimensions tool exposed by this serverMetrics — The Metrics tool exposed by this serverConfiguration is passed through the environment: GOOGLE_APPLICATION_CREDENTIALS, GSC_SITE_URL, DEBUG. 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.
Installation goes through your MCP client rather than a global install: point it at google-search-console-mcp-js on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Google's toolset — Installation, Prerequisites, Dimensions and 1 more — is a fair guide to whether it matches your workflow. It is maintained by sudip358; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Google's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Installation | The Installation tool exposed by this server. |
| Prerequisites | 1. **Google Search Console property** with verified ownership 2. **Google Cloud Project** with Search Console API enabled 3. **Service account credentials** (JSON file) |
| Dimensions | The Dimensions tool exposed by this server. |
| Metrics | The Metrics tool exposed by this server. |
{
"mcpServers": {
"google-search-console-1": {
"command": "npx",
"args": ["-y", "google-search-console-mcp-js"],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "your-value",
"GSC_SITE_URL": "your-value",
"DEBUG": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| GOOGLE_APPLICATION_CREDENTIALS | Configuration value read at startup. | Optional |
| GSC_SITE_URL | Endpoint or connection string the server talks to. | Yes |
| DEBUG | Configuration value read at startup. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.