Google Search Console Mcp Server

Created By
Shin-sibainu8 months ago
A Model Context Protocol (MCP) server that provides programmatic access to Google Search Console API data through Claude Code and Cursor.
Overview

What is Google Search Console MCP Server?

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

How to use Google Search Console MCP Server?

To use the server, configure it by creating a .mcp.json file with your Google OAuth credentials and run the setup command to obtain a refresh token. After configuration, you can use commands in Claude Desktop or Claude Code to interact with the Google Search Console API.

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.
  • Request Google to index or remove URLs.
  • Compare search performance between two time periods.
  • Robust error handling and automatic retry logic.

Use cases of Google Search Console MCP Server?

  1. Accessing and managing multiple Google Search Console properties.
  2. Analyzing search performance data for SEO optimization.
  3. Monitoring sitemap status and URL indexing.
  4. Automating URL submissions for indexing.

FAQ from Google Search Console MCP Server?

  • What is required to set up the server?
    You need to create a project in Google Cloud Console, enable the Google Search Console API, and obtain OAuth 2.0 credentials.

  • Is there a limit on API requests?
    Yes, the daily quota is 2,000 requests per project, with a limit of 600 requests per 100 seconds.

  • What happens if I exceed the API limits?
    The server includes automatic retry logic to handle rate limits and transient failures.

Server Config

{
  "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"
      }
    }
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
Shin-sibainu
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago