google-search-console — Claude Code MCP server: search analytics
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.
claude mcp add google-search-console -e GOOGLE_APPLICATION_CREDENTIALS=<GOOGLE_APPLICATION_CREDENTIALS> -- npx -y @sarahpark/google-search-console-mcpWhat google-search-console 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/[email protected] makes the server available across all your projects.
What it helps with
- 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 for the agent
- Use the
gscserver to list my Search Console properties. - Check the indexing status of
https://example.com/blog/my-post.
How to install google-search-console
Platform CLI
claude mcp add google-search-console -e GOOGLE_APPLICATION_CREDENTIALS=<GOOGLE_APPLICATION_CREDENTIALS> -- npx -y @sarahpark/google-search-console-mcpReplace <…> with your own values
Platform CLI
codex mcp add sarahpark-google-search-console --env GOOGLE_APPLICATION_CREDENTIALS=<GOOGLE_APPLICATION_CREDENTIALS> -- npx -y @sarahpark/google-search-console-mcpReplace <…> with your own values
Config file
{
"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
Config file
{
"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
Platform CLI
gemini mcp add -e GOOGLE_APPLICATION_CREDENTIALS=<GOOGLE_APPLICATION_CREDENTIALS> sarahpark-google-search-console npx -y @sarahpark/google-search-console-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about google-search-console
How do I install google-search-console in Claude Code?
Sign in first with ADC: gcloud auth application-default login --scopes=https://www.googleapis.com/auth/webmasters.readonly,https://www.googleapis.com/auth/cloud-platform, then gcloud auth application-default set-quota-project YOUR_PROJECT_ID. After that add the server with claude mcp add gsc --scope user -- npx -y @sarahpark/[email protected] and restart your client.
What does google-search-console do?
It hands your agent read-only access to Google Search Console data: properties, search analytics, URL indexing details and sitemap status. It cannot change your site or your Search Console settings.
How is signing in as yourself different from a service account?
Application Default Credentials reuse your own Search Console permissions, so you don't add another user to your properties. With a service account you must add its email to every property manually, with Restricted access.
