Skip to main content
Glama
Google Search Console MCP

Google Search Console MCP

How to connect Google Search Console to Claude Code, ChatGPT and any AI agent

Yes, Claude, ChatGPT and other AI agents can work in your Google Search Console account. Google has not published its own Search Console app in the ChatGPT or Claude directories. Cotlet.dev connects your own signed-in Search Console account to any AI agent, so you can ask in plain words and the AI requests indexing and URL removals for you.

What you can ask

Request indexing for acmebakery.com/blog/holiday-cakes-2026 and the 3 product pages I published today.

Remove acmebakery.com/old-menu-2024 from Google results and tell me when the request is submitted.

Check which of my 12 blog posts from this week aren't indexed yet and request indexing for them.

List every URL removal request I made in the last 30 days with its current status.

Every Monday at 9 am, request indexing for the pages I updated the Friday before.

Related MCP server: gsc-mcp-connector

Connect in 2 minutes

Get your API key at https://cotlet.dev/app and export it as COTLET_API_KEY.

Claude Code

claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT

Settings → Apps → add connector URL https://cotlet.dev/mcp/v1, then sign in with Cotlet.dev. No API key needed.

Cursor

Copy .cursor/mcp.json from this repo into your project:

{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}

Run it locally (stdio)

This repo is a real MCP server. It speaks MCP over stdio, lists its Google Search Console tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.

{"mcpServers":{"google-search-console":{"command":"uvx","args":["google-search-console-cotlet-mcp"],"env":{"COTLET_API_KEY":"your-key"}}}}

Or with Docker:

docker build -t google-search-console-mcp .
docker run -i --rm -e COTLET_API_KEY google-search-console-mcp

Tools: google_search_console_guide, google_search_console_status, google_search_console_open, google_search_console_read, google_search_console_click, google_search_console_type, google_search_console_close. Without COTLET_API_KEY a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".

Command line

Python 3.10+, nothing else to install. From PyPI:

pip install google-search-console-cotlet-mcp        # or run it once: uvx google-search-console-cotlet-mcp connect
google-search-console-cotlet-mcp connect

Or straight from this repo:

export COTLET_API_KEY="your-key"
python3 google_search_console_agent.py connect   # ready config for Claude Code, Cursor, ChatGPT
python3 google_search_console_agent.py status    # is Google Search Console ready in your Cotlet.dev account
python3 google_search_console_agent.py guide     # Google Search Console screens and sign-in link
python3 google_search_console_agent.py read      # open Google Search Console, read the page, close the browser
python3 google_search_console_agent.py tools     # list Cotlet.dev tools
python3 google_search_console_agent.py serve     # start the stdio MCP server (same as no argument)

Questions from Google Search Console users

Does Google Search Console have an API?

Google Search Console has an API, but it covers only part of the web interface (checked 16 Oct 2026). It offers Search Analytics queries (with an hourly breakdown for up to 10 days), sitemap list, get, submit and delete, property list, get, add and delete, and read-only URL Inspection of the indexed version. Cotlet.dev works in your own signed-in Google Search Console account, so your AI agent can request indexing and remove URLs with no API key and no code.

How do I connect Google Search Console to ChatGPT?

Add Cotlet.dev as an app in ChatGPT (Settings → Apps, connector URL https://cotlet.dev/mcp/v1), sign in to Google Search Console once in your Cotlet.dev Cloud Browser, and ask ChatGPT in plain words. No code and no Google Search Console API key.

Is there a way to use Claude with Google Search Console?

Yes. In Claude Code run the one-line claude mcp add command above; in the Claude app add https://cotlet.dev/mcp/v1 as a custom connector. Claude then works in your own Google Search Console account.

Is there a Google Search Console MCP server?

Google has not published a Search Console connector in the ChatGPT or Claude directories, only third-party apps are listed there. Cotlet.dev is a hosted MCP server that works in Google Search Console for you, 24/7, with Claude, ChatGPT, Cursor, Codex, n8n, Make and Zapier.

Find it on

Also works with


More: https://cotlet.dev/integrations/google-search-console-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=google-search-console

Start free: https://cotlet.dev/signup?app=google-search-console&utm_source=github&utm_medium=readme&utm_campaign=google-search-console

Available Tools

7 tools
google_search_console_clickBInspect

Click a numbered element on the current Google Search Console page.

Inputs: element (required).

google_search_console_closeAInspect

Close the Google Search Console browser session when the work is done, so credits stop running.

Inputs: no named parameters.

google_search_console_guideBInspect

How to work in Google Search Console (request indexing and remove URLs): its screens and the sign-in link. Call this first.

Inputs: task.

google_search_console_openBInspect

Open a Google Search Console page in your signed-in Cloud Browser (default https://search.google.com) to work with request indexing and remove URLs.

Inputs: url.

google_search_console_readAInspect

Read the current Google Search Console page: its text and numbered buttons, links and fields.

Inputs: element.

google_search_console_statusBInspect

Check that your Cotlet.dev account and Google Search Console are ready: account, credits and Google Search Console connection.

Inputs: no named parameters.

google_search_console_typeBInspect

Type text into a numbered field on the current Google Search Console page.

Inputs: text (required), element (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool maps to a distinct browser-automation action (open/close session, read page, click element, type text), so misselection risk is low. The only mild overlap is between the guide and status tools, since both are pre-flight helpers, but their descriptions clearly separate instructions from account/connection checks.

    Naming Consistency5/5

    All seven tools share the uniform google_search_console_<action> snake_case pattern, with short, predictable action suffixes (guide, status, open, close, read, click, type). No mixed conventions or styles appear anywhere in the set.

    Tool Count5/5

    Seven tools is well within a tight, purposeful scope for a browser-driven GSC client. Every tool earns its place: session lifecycle (open/close), perception (read), interaction (click/type), and onboarding (guide/status), with no redundancy.

    Completeness4/5

    The core loop of open session, read page, click/type, and close is fully covered, plus guide and status for setup. Minor gaps exist: no explicit key-press/submit, scroll, wait-for-load, or direct URL navigation tool, which agents can mostly work around via clicks.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for querying Google Search Console data — search analytics, URL inspection, sitemap monitoring, and more — read-only tools for any MCP-compatible AI client.
      7
      39 PyPI
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted MCP server that exposes Google Search Console tools (list sites, query analytics, inspect URL, list sitemaps) via natural language to AI assistants like ChatGPT and Claude.
      1
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      A production-oriented, read-only Google Search Console MCP server and TypeScript SDK for Claude, Cursor, VS Code, and other MCP clients. Query real Search Console data, inspect indexed URLs, review sitemaps, compare periods, and surface transparent SEO opportunities without handing private data to a third-party SaaS.
      20
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted Google Search Console MCP server that lets ChatGPT, Claude, or other MCP clients query GSC data in natural language. It exposes tools to list sites, query Search Analytics, inspect URLs, and list sitemaps.
      MIT