Search Console

Google Search Console MCP server for Claude, ChatGPT and Cursor

Search Console MCP is a hosted, read-only Google Search Console MCP server. It gives Claude, ChatGPT, Cursor and other AI clients your real clicks, rankings and index status. For site owners, SEO consultants and agencies. Setup takes a minute: paste one URL, sign in with Google. Free plan, then 4.99 € a month.

Works with your AI client

Pick your client for the one-minute setup. One endpoint works everywhere.

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 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 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" }
  }
}

How it works

A remote MCP server over Streamable HTTP: 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 you can ask

Analyst work on your own data, not raw dumps. Paste any of these once you are connected.

All eight SEO use cases

Striking-distance keywords

"Which queries rank between 6 and 20 with real impressions, and which page should I improve for each?"

Keyword cannibalization

"Find queries where two of my pages compete, and tell me which one to keep."

Low-CTR pages

"Which page-one results earn too few clicks? Rewrite their titles from the queries they rank for."

Content decay

"Which pages lost the most clicks against the previous 28 days, and what should I refresh first?"

Index coverage

"Check the URLs in my sitemap and group the ones Google has not indexed by reason."

Weekly SEO report

"Summarize this week: winners, losers, new queries and any technical problems."

+5%

median gain in clicks for paying users’ sites in their first month

+9pts

above each site’s own trend before it connected

Median across 328 properties from 50 paying accounts, each compared with its own trend before it connected. Analysis of 30 September 2026.

The 16 tools

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_sites Every Search Console property your Google account can access. always free
• search_analytics Clicks, impressions, CTR and position: filter by query/page/country/device and compare periods. counts toward quota
• search_insights Striking-distance queries, low-CTR pages, cannibalization, and what rose or fell: ranked and explained. counts toward quota
• search_chart An interactive daily performance chart inside the conversation (Claude). counts toward quota
• inspect_url Index status, coverage, last crawl, canonical and mobile checks for any URL. counts toward quota
• list_sitemaps Submitted sitemaps with status, errors and indexed counts. counts toward quota
• submit_sitemap Submit or re-submit a sitemap so Google re-fetches it. opt-in write
• delete_sitemap Remove a stale sitemap submission from a property. opt-in write
• list_notes Context saved for future sessions: migrations, brand terms, decisions. always free
• add_note Save context for next time: a migration date, brand terms, a decision. always free
• delete_note Remove a note that no longer applies. always free
• page_speed Core Web Vitals & PageSpeed: real-user LCP/INP/CLS plus Lighthouse score and top fixes. counts toward quota
• check_dns DNS records for any domain: A, MX, TXT and more, for ownership and site checks. always free
• check_redirects Trace a URL's redirect chain: every hop, the final destination, loops and chains. always free
• check_robots Is this URL crawlable? robots.txt rules, the matching directive and declared sitemaps. always free
• check_tls TLS certificate health: issuer, expiry, hostname match and chain validity. always free

Hosted or self-hosted?

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 MCP	Local stdio MCP
Transport	Remote · Streamable HTTP (URL)	Local · stdio (subprocess)
Setup	Sign in with Google, paste a URL	Install Python/Node, clone a repo
Google Cloud project	Not needed	You create one + OAuth credentials
Credentials	OAuth, managed for you	You manage a client secret / JSON key
Web & mobile clients	Yes (claude.ai, ChatGPT, Mistral Vibe)	No, desktop/CLI only
Cloud agents (Grok Bot, ChatGPT agents)	Yes, they require a public URL	No, they cannot reach localhost
Updates	Automatic	You pull & redeploy
Access	Read-only by design	Depends on the repo's scopes

Comparing hosted options? See the best hosted Google Search Console MCP servers, or mcpsearchconsole vs mcp-gsc for the self-hosted route.

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.

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
• 3 Search Console properties
• All 16 tools
• Unlimited site checks
• No card required

Connect free

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
• Unlimited Search Console properties
• All 16 tools, no caps
• One Google account
• Stripe billing · cancel anytime

Team

One flat price

29.99 €/mo excl. VAT

For agencies: every client's Search Console in your team's AI, one flat price. 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

Cover your team

What counts as a data pull, the property limit, Team domains and billing: full pricing details.

Who it is for

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.

Search Console MCP for agencies

Content & growth teams

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