Google Search Console MCP server — search analytics, URL inspection, and sitemaps
MCPpedia last refreshed this data
io.github.sarahpark/google-search-console is an MCP server that google Search Console MCP server — search analytics, URL inspection, and sitemaps. Its tool list has not been published yet over stdio, requires no API key, and scores 78/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"gsc": {
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "/absolute/path/to/service-account-key.json"
},
"args": [
"/absolute/path/to/google-search-console-mcp/build/index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Google Search Console MCP server — search analytics, URL inspection, and sitemaps
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in marketing / analytics
Free Google Search Console MCP: your real GSC, Google Analytics and keyword data for AI agents.
DataForSEO API modelcontextprotocol server
Newsletters where you pay for the emails you send, not for dormant subscribers, at a fraction of the price of beehiiv and the like. Open source: self-host it, or use mailcheap.ai.
X/Twitter automation MCP: scrape, post, schedule, analyze, engage. No API key required.
MCP Security Weekly
Get CVE alerts and security updates for io.github.sarahpark/google-search-console and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A minimal MCP server for Google Search Console.
Give Codex, Claude Code, or Claude Desktop read-only access to your search analytics, URL indexing information, and sitemap status. Runs locally; cannot change your site or Search Console settings.
Once connected, ask your agent:
Setup · Tools · Limitations · Troubleshooting
You need Node.js and npm, an MCP client, and access to a Search Console property. To sign in as yourself, also install the Google Cloud CLI. Server startup and tool discovery were checked with Node.js 22.
Create or select a project in Google Cloud Console, then enable the Search Console API. Note the project ID for the next step.
Recommended for new users: sign in as yourself. Application Default Credentials (ADC) use your existing Search Console permissions, so you don't need to add another user to your properties.
Run both commands, replacing YOUR_PROJECT_ID with the project you enabled above:
gcloud auth application-default login \
--scopes=https://www.googleapis.com/auth/webmasters.readonly,https://www.googleapis.com/auth/cloud-platform
gcloud auth application-default set-quota-project YOUR_PROJECT_ID
The quota project is required. For permission or scope errors, see troubleshooting.
[!CAUTION] Store the key outside your repo and never commit it. Use its absolute path in your client's configuration below.
If Search Console rejects the email with "Failed to add user: email not found," sign in as yourself instead; see troubleshooting.
The server checks GOOGLE_APPLICATION_CREDENTIALS before local ADC. If switching to ADC, remove an old key-path setting from your client configuration and environment.
The npx commands in the next step download and run version 1.1.0 for you. Both authentication methods work with the npm package; no clone or build is required.
git clone https://github.com/sarahpark/google-search-console-mcp.git
cd google-search-console-mcp
npm install
npm run build
In the client commands below, replace npx -y @sarahpark/google-search-console-mcp@1.1.0 with node "/absolute/path/to/google-search-console-mcp/build/index.js". In Claude Desktop, set command to node and args to an array containing that absolute path. Run npm test for offline authentication checks.
After completing authentication, paste this into your agent:
Add
npx -y @sarahpark/google-search-console-mcp@1.1.0asgscin this client's user-level MCP config, preserving existing servers. Use my local Application Default Credentials. Tell me when setup is complete and whether I need to restart the client.
For a service account, replace "Use my local Application Def