Google Search Console Mcp Server

by Shin-sibainu

295 downloads

Not rated

GitHub

About

A Model Context Protocol (MCP) server that provides programmatic access to Google Search Console API data through Claude Code and Cursor.

Details

Author: Shin-sibainu
Downloads: 295
Categories: Search

- List all Search Console properties you have access to
- Query search performance data with flexible filtering
- Retrieve sitemap status and indexing statistics
- Check detailed indexing status of specific URLs
- Submit URLs for indexing or removal
- Compare search performance between two time periods

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Google Search Console Mcp Server

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

From the repository

Configure a .mcp.json file with your Google OAuth credentials (GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REDIRECT_URI, GOOGLE_REFRESH_TOKEN). Run the setup command (npx -y google-search-console-mcp-setup) to generate a refresh token, then use natural language prompts in Claude Desktop or Claude Code to interact with Search Console data.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "google search console mcp server": {
            "google-search-console": {
                "command": "npx",
                "args": [
                    "google-search-console-mcp-server"
                ],
                "env": {
                    "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
                    "GOOGLE_CLIENT_SECRET": "your-client-secret",
                    "GOOGLE_REDIRECT_URI": "http://localhost:8080",
                    "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
                }
            }
        }
    }
}

McpServers

{
    "google-search-console": {
        "command": "npx",
        "args": [
            "google-search-console-mcp-server"
        ],
        "env": {
            "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
            "GOOGLE_CLIENT_SECRET": "your-client-secret",
            "GOOGLE_REDIRECT_URI": "http://localhost:8080",
            "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
        }
    }
}

Google Search Console MCP Server

A Model Context Protocol (MCP) server that provides programmatic access to Google Search Console API data through Claude Code and Cursor.

Quick Start

New to this MCP server? Jump to Step-by-Step Setup Guide for complete instructions.

Features

- 🔍 List Sites - Get all Search Console properties you have access to - 📊 Search Analytics - Query search performance data with flexible filtering - 🗺️ Sitemap Information - Retrieve sitemap status and indexing statistics - 🔎 URL Inspection - Check detailed indexing status of specific URLs - 📤 Submit URL for Indexing - Request Google to index or remove URLs - 📈 Compare Periods - Compare search performance between two time periods - 🛡️ Robust Error Handling - Detailed error messages with actionable guidance - 🔄 Automatic Retry Logic - Handles rate limits and transient failures - ✅ Input Validation - Validates all parameters before API calls

Setup

1. Configure Claude Code

Create .mcp.json in your project root: ``

json
{
  "mcpServers": {
    "google-search-console": {
      "command": "npx",
      "args": ["google-search-console-mcp-server"],
      "env": {
        "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com",
        "GOOGLE_CLIENT_SECRET": "your-client-secret",
        "GOOGLE_REDIRECT_URI": "http://localhost:8080",
        "GOOGLE_REFRESH_TOKEN": "your-refresh-token"
      }
    }
  }
}



2. Get Google OAuth Credentials


1. Go to Google Cloud Console
2. Create a project and enable Google Search Console API (and optionally Indexing API)
3. Create OAuth 2.0 Client ID (Desktop app)
4. Add

http://localhost:8080

 to Authorized redirect URIs
5. Add your email to Test users in OAuth consent screen

3. Get Refresh Token


Run the setup command and follow the browser authentication flow:

bash
npx -y google-search-console-mcp-setup



You'll be prompted to enter your

GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and GOOGLE_REDIRECT_URI

.

Copy the

GOOGLE_REFRESH_TOKEN from the output and paste it into your .mcp.json

.

Reload Claude Code window.

Usage


Once configured, you can use the tools in Claude Desktop or Claude Code:


Show me my Google Search Console sites

or


Get search performance data for example.com for the last 7 days



Available Tools

`1.` list_sites



Get all Search Console sites you have access to.

Parameters: None

Example:


Search Consoleのサイト一覧を教えて

`2.` get_analytics



Query search performance data for a specified date range.

Parameters:

-

siteUrl

 (required): Site URL (e.g., "https://example.com/")
-

startDate

 (required): Start date (YYYY-MM-DD)
-

endDate

 (required): End date (YYYY-MM-DD)
-

dimensions

 (optional): Array of dimensions ["query", "page", "country", "device", "searchAppearance"]
-

rowLimit

 (optional): Max rows (default: 100, max: 25000)
-

startRow

 (optional): Starting row for pagination

Example:


example.comの過去7日間のトップクエリを取得して

example.comの2025年1月1日から1月31日までの、
ページ別とデバイス別のパフォーマンスを500件取得して

`3.` get_sitemaps



Retrieve sitemap information for a site.

Parameters:

-

siteUrl

 (required): Site URL

Example:


example.comのサイトマップ情報を確認して

`4.` inspect_url



Inspect the indexing status of a specific URL.

Parameters:

-

siteUrl

 (required): Site URL (e.g., "https://example.com/")
-

inspectionUrl

 (required): Full URL to inspect

Example:


https://example.com/blog/article のインデックス状態を検査して

`5.` submit_url_for_indexing



Submit a URL to Google for indexing or request URL removal using the Indexing API.

Parameters:

-

url

 (required): Full URL to submit (e.g., "https://example.com/page")
-

type

 (optional): Notification type - "URL_UPDATED" (default) or "URL_DELETED"

Example:


https://example.com/new-article をインデックスに送信して

https://example.com/old-page を削除申請して（type: URL_DELETED）



Note: Requires Indexing API to be enabled in Google Cloud Console and the

https://www.googleapis.com/auth/indexing

 scope.

`6.` compare_periods



Compare search performance metrics between two time periods (e.g., this week vs last week).

Parameters:

-

siteUrl

 (required): Site URL (e.g., "https://example.com/")
-

currentStartDate

 (required): Current period start date (YYYY-MM-DD)
-

currentEndDate

 (required): Current period end date (YYYY-MM-DD)
-

previousStartDate

 (required): Previous period start date (YYYY-MM-DD)
-

previousEndDate

 (required): Previous period end date (YYYY-MM-DD)
-

dimensions

 (optional): Array of dimensions to group by
-

rowLimit

 (optional): Max rows (default: 100, max: 25000)

Example:


Compare this week vs last week performance for example.com

Compare query performance for example.com between January 2025 and December 2024
(currentStartDate: 2025-01-01, currentEndDate: 2025-01-31,
 previousStartDate: 2024-12-01, previousEndDate: 2024-12-31,
 dimensions: ["query"])



API Limits


- Daily quota: 2,000 requests per project
- Per 100 seconds: 600 requests
- Data availability: Up to 16 months of historical data
- Data latency: Typically 2-3 days

Error Handling & Retry Logic


This MCP server includes comprehensive error handling:

Automatic Retries


- Rate Limiting (429): Automatically retries with exponential backoff
- Server Errors (5xx): Retries up to 3 times with increasing delays
- Transient Failures: Smart retry logic with jitter to prevent thundering herd

Input Validation


All tools validate inputs before making API calls:

- Site URL: Validates URL format and structure
- Dates: Validates YYYY-MM-DD format and logical date ranges
- Row Limits: Ensures limits are within API constraints (1-25,000)

Detailed Error Messages


Error messages include:

- Clear description of what went wrong
- HTTP status code
- Actionable steps to resolve the issue

Example:


Access denied for list sites (403)
Verify your authentication credentials and ensure you have access to this Search Console property.
You may need to add your account as a test user in Google Cloud Console.



Troubleshooting


"Missing required environment variables"


Make sure your

.env file exists and contains valid GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET

.

"redirect_uri_mismatch"


Ensure

http://localhost:8080

 is added to Authorized redirect URIs in Google Cloud Console.

"Error 403: access_denied"


Add your Google account email to the Test users section in OAuth consent screen.

"Invalid site URL format"


Site URLs must be complete URLs like:

-

https://example.com/

 (for URL-prefix properties)
-

sc-domain:example.com

 (for domain properties)

"Date range too old"


Search Console data is only available for the last 16 months.

"Rate limit exceeded"


The tool will automatically retry with backoff. If you continue to hit limits:

- Wait a few minutes between requests
- Reduce

rowLimit

 in analytics queries
- API Limits: 2,000 requests/day, 600 requests/100 seconds

Token Expired


Re-run the authentication setup:

bash
node build/auth/setup-auth.js



Development


Build

bash
npm run build



Watch Mode

bash
npm run dev



Re-authenticate

bash
node build/auth/setup-auth.js



Project Structure


src/
├── index.ts                 # MCP server entry point
├── auth/
│   ├── google-auth.ts       # OAuth 2.0 client
│   └── setup-auth.ts        # Authentication CLI
├── tools/
│   ├── list-sites.ts        # List sites tool
│   ├── get-analytics.ts     # Search analytics tool
│   ├── get-sitemaps.ts      # Sitemap info tool
│   ├── inspect-url.ts       # URL inspection tool
│   ├── submit-url.ts        # Submit URL for indexing
│   └── compare-periods.ts   # Compare time periods
├── types/
│   └── index.ts             # Type definitions
└── utils/
    └── error-handler.ts     # Error handling & validation



Security Notes


- Never commit

.env or .mcp.json

 files to version control
- Keep your refresh token secure
- Use readonly scope (

webmasters.readonly`) when possible - Refresh tokens provide persistent access - store them securely

License

MIT

Contributing

Contributions are welcome! Please feel free to submit issues or pull requests. ---

Resources

- Google Search Console API Documentation - Model Context Protocol - Claude Code Documentation

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

Claude Desktop / Cursor

McpServers

Google Search Console MCP Server

Quick Start

Features

Setup

1. Configure Claude Code

2. Get Google OAuth Credentials

3. Get Refresh Token

Usage

Available Tools

1. list_sites

2. get_analytics

3. get_sitemaps

4. inspect_url

5. submit_url_for_indexing

6. compare_periods

API Limits

Error Handling & Retry Logic

Automatic Retries

Input Validation

Detailed Error Messages

Troubleshooting

"Missing required environment variables"

"redirect_uri_mismatch"

"Error 403: access_denied"

"Invalid site URL format"

"Date range too old"

"Rate limit exceeded"

Token Expired

Development

Build

Watch Mode

Re-authenticate

Project Structure

Security Notes

License

Contributing

Resources

Install

More like this

Brave Search

🔎 GPT Researcher

Github SSE

AWS MCP Servers

Yoyo

whatsapp-mcp

`1.` list_sites

`2.` get_analytics

`3.` get_sitemaps

`4.` inspect_url

`5.` submit_url_for_indexing

`6.` compare_periods