Google Search Console MCP

A secure, community-maintained Model Context Protocol server for Google Search Console. It gives MCP clients structured access to Search Analytics, properties, sitemaps, and URL Inspection.

Features

• Query clicks, impressions, CTR, and average position.

• List and inspect Search Console properties.

• List and inspect submitted sitemaps.

• Inspect the indexed version of a URL.

• Return both readable text and structured MCP output.

• Restrict access to an explicit property allowlist.

• Keep sitemap mutation tools disabled by default.

• Authenticate with a service account or Google Application Default Credentials.

• Install with npx; no global package installation is required.

Related MCP server: mcp-google-search-console-crunchtools

Requirements

• Node.js 22.14 or newer.

• A Google Cloud project with the Search Console API enabled.

• A Google identity that has access to at least one Search Console property.

• An MCP client such as Claude Code.

Quick start

1. Prepare Google credentials

For a service account:

1. Enable the Google Search Console API in a Google Cloud project.

2. Create a service account and download its JSON key.

3. In Google Search Console, add the service account email under Settings → Users and permissions for each property it should access.

See Authentication for Application Default Credentials and detailed setup instructions.

2. Run the setup wizard

npx -y google-search-console-mcp setup

The wizard validates Google access, stores only the credential file path in the user configuration directory, and registers the MCP server with Claude Code at user scope.

Non-interactive setup is also supported:

npx -y google-search-console-mcp setup \
  --credentials /absolute/path/to/service-account.json \
  --allowed-sites sc-domain:example.com,https://www.example.com/ \
  --non-interactive

On Windows PowerShell, use one line or PowerShell backticks instead of backslashes.

3. Use it from Claude Code

Restart Claude Code after setup, then try:

List my Google Search Console properties.
Show clicks and impressions for the last 28 days, grouped by query.
Inspect https://www.example.com/article for indexing issues.
List the sitemaps submitted for sc-domain:example.com.

Run diagnostics at any time:

npx -y google-search-console-mcp doctor

Manual Claude Code registration

macOS and Linux:

claude mcp add google-search-console --scope user \
  --env GSC_CREDENTIALS_FILE=/absolute/path/to/service-account.json \
  -- npx -y google-search-console-mcp

Windows:

claude mcp add google-search-console --scope user --env GSC_CREDENTIALS_FILE=C:\path\to\service-account.json -- cmd /c npx -y google-search-console-mcp

See Client setup for project-level JSON configuration.

Tools

URL Inspection does not run a live test and cannot request indexing. Google does not expose those actions through the Search Console API.

See the complete Tool reference.

Configuration

Environment variables take precedence over the stored user configuration. See Configuration.

Security defaults

• Read-only Google scope unless write tools are enabled.

• No credentials or API response data are written to logs.

• Logs go to stderr so MCP stdio messages remain valid.

• Write tools are absent from the tool list unless explicitly enabled.

• Property access can be constrained with GSC_ALLOWED_SITES.

• No telemetry.

Read Security model and Security policy before enabling write tools.

Development

git clone https://github.com/dienhokhanh/google-search-console-mcp.git
cd google-search-console-mcp
npm install
npm run check

Run the development server:

npm run dev

See Development and Contributing.

License

MIT