Connect Google Search Console to your AI.

Connect Google Search Console to Claude

  1. Open Settings → Connectors in Claude Desktop or claude.ai.
  2. Click Add custom connector and paste the URL below.
  3. Click Add, then sign in with Google when prompted.
https://mcpsearchconsole.com/mcp

Connect Google Search Console to Claude Code

Add the server from your terminal:

claude mcp add --transport http search-console https://mcpsearchconsole.com/mcp

Run /mcp inside Claude Code and complete Google sign-in.

Connect Google Search Console to ChatGPT

  1. Go to Settings → Connectors and enable Developer mode.
  2. Click Create / Add custom MCP server and paste the URL below.
  3. Authenticate with Google to finish.
https://mcpsearchconsole.com/mcp

Connect Google Search Console to Codex

Add this to ~/.codex/config.toml:

[mcp_servers.search-console]
url = "https://mcpsearchconsole.com/mcp"

On Google sign-in, Codex opens your browser to authorize. (If your Codex version only supports stdio servers, bridge it with npx mcp-remote https://mcpsearchconsole.com/mcp.)

Connect Google Search Console to Grok Bot

  1. Sign in with Google here and click Generate setup token (Grok Bot can't run the OAuth sign-in itself yet).
  2. In Grok Bot, open Settings → Plugins, add a custom connector, and paste the URL below.
  3. Set the auth header to Authorization: Bearer <your token>, save, then attach the tools to a task with @.
https://mcpsearchconsole.com/mcp

Connect Google Search Console to Mistral Vibe

  1. In Mistral Vibe → Settings → Connectors, choose Add MCP connector.
  2. Paste the URL below and save.
  3. Sign in with Google when prompted.
https://mcpsearchconsole.com/mcp

Connect Google Search Console to Cursor

Add to ~/.cursor/mcp.json (or Settings → MCP → Add server):

{
  "mcpServers": {
    "search-console": { "url": "https://mcpsearchconsole.com/mcp" }
  }
}

Reload, then authorize with Google from the MCP panel.

Connect Google Search Console to any MCP client

Any client that supports remote MCP servers over Streamable HTTP. Point it at the URL and it handles Google sign-in via OAuth.

{
  "mcpServers": {
    "search-console": { "type": "streamable-http", "url": "https://mcpsearchconsole.com/mcp" }
  }
}

Connect Search Console to AI in three steps

The hosted, read-only Google Search Console MCP server brings your real search performance data into Claude, ChatGPT, Claude Code and Cursor. A remote MCP connector for Google Search Console: point your client at one URL and go. No install, no API keys, connected in about a minute.

1

Pick your AI client

Use the setup tabs above for Claude, Claude Code, ChatGPT, Codex, Grok Bot, Mistral Vibe, Cursor and more.

2

Add the MCP endpoint

Drop the hosted MCP URL into your client and authorize with Google when prompted.

3

Ask about your traffic

"Which queries are rising?" "What pages lost clicks?" Your AI answers from your real GSC data.

What your AI can do with it

A focused Search Console connector: the data that actually answers SEO questions.

List your properties

Every Search Console site your Google account can access, read-only.

Search analytics

Clicks, impressions, CTR and position, filtered by query, page, country or device, with period-over-period comparison.

Inspect & diagnose

Check any URL's index status, coverage, canonical and last crawl, plus the sitemaps you've submitted and their errors. Opt in to write access and your AI can submit or re-submit sitemaps too.

Speed & site health

Core Web Vitals and PageSpeed, redirect chains, robots.txt crawlability, DNS and TLS certificates: the technical health behind your rankings.

Find opportunities

Striking-distance keywords, rising and falling pages, low-CTR wins. Analyst work, not raw dumps.

Works everywhere

Remote MCP over Streamable HTTP: Claude, Cursor, Windsurf, ChatGPT. No install.

The perfect tool for SEO specialists

Built for people who answer to rankings: consultants, agencies and in-house teams.

SEO specialists & consultants

Run audits, find striking-distance keywords and explain ranking changes from live Search Console data, inside the AI you already work with. No CSV exports, no spreadsheets.

Agencies

Every client property your Google account can access is available through one connector. The Team plan covers your whole company via your email domain: one invoice, no seats.

Content & growth teams

Weekly content plans grounded in real query data, cannibalization sweeps before publishing, and traffic-drop triage in minutes instead of meetings.

The tools it exposes

Exactly what the MCP server offers your AI: read-only by default, with sitemap submission as an opt-in. Property discovery and site checks are always free; data pulls count toward the free quota.

  • list_sitesEvery Search Console property your Google account can access.
    always free
  • search_analyticsClicks, impressions, CTR and position: filter by query/page/country/device and compare periods.
    counts toward quota
  • search_insightsStriking-distance queries, low-CTR pages, cannibalization, and what rose or fell: ranked and explained.
    counts toward quota
  • search_chartAn interactive daily performance chart inside the conversation (Claude).
    counts toward quota
  • inspect_urlIndex status, coverage, last crawl, canonical and mobile checks for any URL.
    counts toward quota
  • list_sitemapsSubmitted sitemaps with status, errors and indexed counts.
    counts toward quota
  • submit_sitemapSubmit or re-submit a sitemap so Google re-fetches it.
    opt-in write
  • delete_sitemapRemove a stale sitemap submission from a property.
    opt-in write
  • list_notesContext saved for future sessions: migrations, brand terms, decisions.
    always free
  • add_noteSave context for next time: a migration date, brand terms, a decision.
    always free
  • delete_noteRemove a note that no longer applies.
    always free
  • page_speedCore Web Vitals & PageSpeed: real-user LCP/INP/CLS plus Lighthouse score and top fixes.
    counts toward quota
  • check_dnsDNS records for any domain: A, MX, TXT and more, for ownership and site checks.
    always free
  • check_redirectsTrace a URL's redirect chain: every hop, the final destination, loops and chains.
    always free
  • check_robotsIs this URL crawlable? robots.txt rules, the matching directive and declared sitemaps.
    always free
  • check_tlsTLS certificate health: issuer, expiry, hostname match and chain validity.
    always free

Pricing

Free to connect. Unlimited when you need it.

Connect free and pull real data today. Go Solo for unlimited data pulls, or Team to cover everyone on your company domain.

Free

No card
0 €

Connect your Search Console and put real data in your AI today.

  • 15 data pulls/day · 40/month, per person or per company domain
  • All 9 tools
  • Unlimited property discovery & site checks
  • No card required

Solo

Most popular
4.99 €/mo excl. VAT

Unlimited data pulls for the price of a coffee. Upgrade from your account page.

  • Unlimited data pulls
  • All 9 tools, no caps
  • One Google account
  • Stripe billing · cancel anytime

Team

One flat price
29.99 €/mo excl. VAT

Cover your whole company with one subscription. No seats to manage, no invites to send.

  • Everything in Solo, for the whole team
  • Google Workspace domains verify on sign-in; others via one DNS record
  • Everyone on the domain covered automatically
  • Shared notes: context every teammate’s AI can read
  • No seats, no invites, one invoice
  • Up to 10 domains

Read-only by design

The least-privilege Google scope by default, write access only when you opt in, managed OAuth, and nothing stored that doesn't need to be.

Read-only, by scope

Sign-in requests only Google's webmasters.readonly scope: it can read your Search Console data but cannot modify your site or change settings. Sitemap submission is a separate opt-in consent you can grant later, and it unlocks nothing else.

OAuth, managed for you

Sign in with Google and you're done. No API keys, no client secrets, no Google Cloud project to create or leak.

Tokens encrypted at rest

Your Google refresh token is encrypted with AES-256-GCM, with the key held outside the database.

Site checks stay public

The site-health tools (DNS, redirects, robots.txt, TLS, PageSpeed) only read public web data. They never touch your Google account.

Hosted MCP vs local stdio MCP

Open-source Search Console MCP servers run locally over stdio. This one is hosted and remote (Streamable HTTP).

  • Hosted, not self-host: skip the Python/Node + Google Cloud setup that open-source GSC MCP servers require.
  • Read-only by design: the least-privilege scope means this SEO MCP can read your data but never touch your site.
  • One AI connection to Search Console: the same endpoint works across every MCP-capable client.
This hosted MCPLocal stdio MCP
TransportRemote · Streamable HTTP (URL)Local · stdio (subprocess)
SetupSign in with Google, paste a URLInstall Python/Node, clone a repo
Google Cloud projectNot neededYou create one + OAuth credentials
CredentialsOAuth, managed for youYou manage a client secret / JSON key
Web & mobile clientsYes (claude.ai, ChatGPT, Mistral Vibe)No, desktop/CLI only
Cloud agents (Grok Bot, ChatGPT agents)Yes, they require a public URLNo, they cannot reach localhost
UpdatesAutomaticYou pull & redeploy
AccessRead-only by designDepends on the repo's scopes

Frequently asked questions

Google Search Console MCP, hosted connectors and remote MCP servers. Still unsure? Ask us, we answer.

Put your search data in your AI

Free to connect · read-only · about a minute to set up.