GSC-MCP-Server

Google Search Console MCP Server — Connect Google Search Console to Claude, Cursor, and other MCP clients.

Features

• 🔍 Search Analytics — Query clicks, impressions, CTR, and position data

• 📊 SEO Opportunities — Find low-CTR keywords, detect cannibalization issues

• 📈 Reports — Weekly summaries, period comparisons

• 🗺️ Sitemaps — List, submit, and manage sitemaps

• 🔎 URL Inspection — Check indexing status (requires full scope)

• 💾 Caching — SQLite cache for faster repeated queries

• 🔐 Secure — OAuth tokens stored in OS keychain

Quick Start

Prerequisites

1. Create Google Cloud OAuth Credentials

You need to create your own OAuth credentials in Google Cloud Console:

1. Go to Google Cloud Console

2. Create a new project or select an existing one

3. Enable the Google Search Console API:

   • Go to "APIs & Services" → "Library"

   • Search for "Google Search Console API"

   • Click "Enable"

4. Create OAuth credentials:

   • Go to "APIs & Services" → "Credentials"

   • Click "Create Credentials" → "OAuth client ID"

   • Choose "Desktop application"

   • Name it (e.g., "GSC-MCP")

   • Click "Create"

5. Copy the Client ID and Client Secret

6. Add test users (required while app is in testing mode):

   • Go to "APIs & Services" → "OAuth consent screen"

   • Scroll to "Test users" section

   • Click "Add users"

   • Add the Google account email(s) you'll use to authenticate

   • Click "Save"

Note: While your app's publishing status is "Testing", only test users can authenticate. You can add up to 100 test users.

2. Configure GSC-MCP

Run the init command and enter your credentials:

This will:

• Prompt for your Client ID and Client Secret

• Open a browser for Google authentication

• Store your refresh token securely in the OS keychain

Usage

CLI Commands

MCP Client Configuration

Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

VS Code (Copilot)

Add to your VS Code MCP settings (~/.vscode/mcp.json or workspace settings):

Cursor

Add to your Cursor MCP config:

Available Tools

Search Analytics

Sitemaps

URL Inspection

SEO Opportunities

Export

Resources

The server exposes browsable resources:

• gsc://sites — List all properties

• gsc://sites/{siteUrl}/sitemaps — List sitemaps for a property

Scopes

GSC-MCP supports two permission levels:

Readonly (default)

• Search analytics queries

• List sitemaps

• SEO analysis tools

Full

• Everything in readonly, plus:

• Submit/delete sitemaps

• URL inspection

Configuration Files

GSC-MCP stores configuration in platform-specific locations:

Files:

• config.json — OAuth client ID/secret, scope settings

• cache.sqlite — Query cache and saved presets

Tokens are stored securely in the OS keychain when available.

Service Account Setup

For automated/server use, you can use a service account instead of OAuth:

1. Create a service account in Google Cloud Console

2. Download the JSON key file

3. Add the service account email as an owner in Google Search Console

4. Initialize:

API Quotas

Google Search Console API has a default quota of 1,200 queries per day. GSC-MCP includes:

• Automatic retry with exponential backoff

• Query caching to reduce API calls

• Pagination handling for large result sets

Examples

Find Quick-Win Keywords

Weekly Report

Compare Periods

Export Data

Development

License

MIT

Contributing

Contributions are welcome! Please open an issue or PR.

Credits

Built with:

• @modelcontextprotocol/sdk

• googleapis

• commander

• better-sqlite3