Google Search Console MCP server

Google Search Console MCP Server

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:

• "Which queries had the most impressions but few clicks over the last 28 days?"
• "Compare mobile vs desktop search performance this month."
• "Check the indexing status of https://example.com/blog/my-post."

Setup · Tools · Limitations · Troubleshooting

Setup

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.

1. Enable the Google API

Create or select a project in Google Cloud Console, then enable the Search Console API. Note the project ID for the next step.

2. Authenticate

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 YOURPROJECTID 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.

Alternative: use a service account key

1. In Google Cloud Console, go to APIs & Services → Credentials → Create Credentials → Service account. Name it and finish creation; you can skip the optional role/access steps.
2. Open the service account, then Keys → Add Key → Create new key → JSON to download a key.
3. In Search Console, open each property's Settings → Users and permissions → Add user. Add the service account email with Restricted access.

[!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 GOOGLEAPPLICATIONCREDENTIALS before local ADC. If switching to ADC, remove an old key-path setting from your client configuration and environment.

3. Install the server

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.

Optional: build from source

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.

Let Codex or Claude Code handle installation and configuration

After completing authentication, paste this into your agent:

Add npx -y @sarahpark/google-search-console-mcp@1.1.0 as gsc in 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.

Shortened. The full README is on GitHub.