Google Search Console MCP server — search analytics, URL inspection, and sitemaps
A Model Context Protocol (MCP) server that gives AI agents direct access to your Google Search Console data.
Read-only access — this server cannot submit URLs, modify settings, or make any changes to your Search Console properties.
[!IMPORTANT] This server uses service account authentication. The service account must be added as a user on each Search Console property you want to access.
List all sites (properties) you have access to in Google Search Console.
No parameters required.
</details> <details> <summary><code>search_analytics</code></summary>Query search analytics data — clicks, impressions, CTR, and position.
| Parameter | Type | Required | Description |
|---|---|---|---|
siteUrl | string | Yes | Site URL as it appears in Search Console (e.g. https://example.com/ or sc-domain:example.com) |
startDate | string | Yes | Start date in YYYY-MM-DD format |
endDate | string | Yes | End date in YYYY-MM-DD format |
dimensions | string | No | Comma-separated: query, page, country, device, searchAppearance, date |
rowLimit | number | No | Max rows to return (default 100, max 25000) |
searchType | string | No | web, image, video, news, discover, or googleNews (default web) |
queryFilter | string | No | Filter by query. Prefix with regex: for regex matching |
pageFilter | string | No | Filter by page URL. Prefix with regex: for regex matching |
countryFilter | string | No | ISO 3166-1 alpha-3 country code (e.g. USA, GBR) |
deviceFilter | string | No | DESKTOP, MOBILE, or TABLET |
Check indexing status, crawl info, and mobile usability for a URL.
| Parameter | Type | Required | Description |
|---|---|---|---|
siteUrl | string | Yes | Site URL as it appears in Search Console |
inspectionUrl | string | Yes | The full URL to inspect (must belong to the site) |
List all submitted sitemaps and their status for a site.
| Parameter | Type | Required | Description |
|---|---|---|---|
siteUrl | string | Yes | Site URL as it appears in Search Console |
Already have your service account key? Paste this prompt into Claude Code or Claude Desktop and it will configure everything for you:
Clone and build the Google Search Console MCP server from https://github.com/sarahpark/google-search-console-mcp, then add it to my global MCP config. My service account key is at
/path/to/service-account-key.json. After setup, calllist_sitesto verify it works.
Replace the key path with your actual file location.
git clone https://github.com/sarahpark/google-search-console-mcp.git
cd google-search-console-mcp
npm install
npm run build.json key file will download — save it somewhere safe (e.g. ~/.config/gcloud/service-account-key.json)[!CAUTION] Treat this key file like a secret key. Do not save it inside your project repo or commit it to git. Store it outside your project directory and reference it by absolute path in your MCP config.
name@project-id.iam.gserviceaccount.com — you can find it on the service account details page)Add to your claude_desktop_config.json:
{
"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"
}
}
}
}Add to the "mcpServers" object in ~/.claude.json:
{
"mcpServers": {
"gsc": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/google-search-console-mcp/build/index.js"],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "/absolute/path/to/service-account-key.json"
}
}
}
}Once configured, ask Claude naturally:
MIT