How to Use the Google Search Console MCP in Claude

Q: How do I connect Google Search Console to Claude Desktop?

Open your claudedesktopconfig.json file and add this MCP server configuration with your Google credentials. Once you restart Claude Desktop, your agent will immediately have access to tools like listsites and querysearchanalytics.

Q: Can Claude Desktop submit new sitemaps to Google Search Console?

Yes. Your Claude Desktop agent uses the submitsitemap tool to register new sitemaps directly into Google Search Console.

Q: Can I query Google Search Console traffic statistics inside Claude Desktop?

Yes. Your agent uses querysearchanalytics to pull impressions and clicks directly into your Claude Desktop chat window.

Q: How does Claude Desktop handle API rate limits for Google Search Console?

Google limits how often you run tools like inspecturl inside Google Search Console. If your Claude Desktop agent hits an API rate limit, it receives a standard error code and asks you to wait before running more diagnostics.

Get real-time Google Search Console performance data and index status directly in your Claude Desktop chat window.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Google Search Console MCP to Claude Desktop

Create your Vinkius account to connect Google Search Console to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Google Search Console with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Fix Indexing Blocks inside Claude Desktop

The `inspect_url` tool exposes the exact indexing status of any page directly to your Claude Desktop chat. Instead of manually digging through the Search Console web interface, your Claude Desktop agent runs this diagnostic check to find mobile usability errors, canonical issues, or crawl blocks. This setup lets you pass raw Search Console inspection payloads directly into your Claude Desktop chat. When Claude Desktop spots a crawl error, you can immediately write a fix in your local files or test the corrected code on localhost before committing.

Automate Sitemap Deployment via MCP Server

The `submit_sitemap` tool lets your agent register new XML indexes to Google without you leaving Claude Desktop. If you launch a new product collection, your agent calls this tool alongside `delete_sitemap` to swap out stale indexes. You run this Search Console workflow directly through the Claude Desktop configuration. Claude Desktop reads your local build output, detects new sitemap files, and updates Google Search Console in one quick chat command.

Pull Search Analytics into Your Chat

The `query_search_analytics` tool pulls raw click, impression, and click-through rate data directly into Claude Desktop. Look, here's the kicker: you don't have to export CSVs and upload them because the agent queries the API directly to analyze ranking drops on the fly. This lets you build instant Search Console reports directly inside your Claude Desktop workspace. Tell your agent to compare last week's Google Search Console performance data, and Claude Desktop will run the query and present the winners and losers in a clean table.

Setup guide

Set up Google Search Console MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Google Search Console MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Google Search Console MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under google-search-console-mcp.

json

{
  "mcpServers": {
    "google-search-console-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Google Search Console. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Google Search Console now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Google Search Console MCP in Claude Desktop

Open your `claude_desktop_config.json` file and add this MCP server configuration with your Google credentials. Once you restart Claude Desktop, your agent will immediately have access to tools like `list_sites` and `query_search_analytics`.

Yes. Your Claude Desktop agent uses the `submit_sitemap` tool to register new sitemaps directly into Google Search Console.

Yes. Your agent uses `query_search_analytics` to pull impressions and clicks directly into your Claude Desktop chat window.

Google limits how often you run tools like `inspect_url` inside Google Search Console. If your Claude Desktop agent hits an API rate limit, it receives a standard error code and asks you to wait before running more diagnostics.

Your Google Search Console analytics and site verification data remain private because the connection runs through a secure V8 isolate sandbox. Claude Desktop only accesses this data when you explicitly ask your agent to run a tool like `query_search_analytics`.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript