MCP.so
Sign In
G

Google Search Console MCP Server

@Shin-sibainu

Basic information

Category

Search

Transports

stdio

Author

Shin-sibainu

Submitted by

Shin-sibainu

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

Google Search Console MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "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 tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is 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. It enables developers to query search performance, manage sitemaps, inspect URLs, and submit URLs for indexing using natural language commands.

How to use Google Search Console MCP Server?

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.

Key features of Google Search Console MCP Server

  • 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

Use cases of Google Search Console MCP Server

  • Get top queries and performance data for a site over the last 7 days
  • Compare this week's search performance vs last week
  • Inspect the indexing status of a specific page
  • Submit a new article URL for indexing
  • Review sitemap submission status and errors

Frequently asked questions

1

What are the API limits for the Google Search Console MCP Server?

Daily quota is 2,000 requests per project, with a maximum of 600 requests per 100 seconds. Data is available for up to 16 months with a typical latency of 2-3 days.

2

How do I get OAuth credentials?

Create a project in Google Cloud Console, enable the Google Search Console API (and optionally the Indexing API), create an OAuth 2.0 Client ID (Desktop app), and add `http://localhost:8080` as an authorized redirect URI.

3

What authentication is required?

OAuth 2.0 with a client ID, client secret, redirect URI, and a refresh token. The refresh token is obtained by running the `google-search-console-mcp-setup` command and completing the browser authentication flow.

4

How do I handle "403 access_denied" errors?

Add your

Comments

More Search MCP servers