Google Search Console MCP

A Google Search Console MCP server for your AI, nothing to install

Connect Search Console once, read-only, and Claude, ChatGPT, Cursor or Claude Code can read your queries, pages, indexing and sitemaps and answer in plain words. No server, no plugin, all 16 months of history Google keeps. Free for one site.

Works with Claude, Claude Code, ChatGPT and Cursor.

How your AI does it

  1. STEP 1

    Connect Google

    Sign up, open Search Console in the dashboard and sign in with Google. AskYourStack asks only for the read-only Search Console permission.

  2. STEP 2

    Pick your properties

    Choose which verified properties your AI may read, up to your plan's limit. Agency connects up to three Google accounts, for clients who keep their own.

  3. STEP 3

    Add the address to your AI

    One address for every client: https://askyourstack.com/mcp. Then ask: "Why did clicks drop last week?" Your AI compares the periods, finds the losing pages and queries, checks Google's update history and inspects the URLs.

What your AI can read

  • Clicks, impressions, CTR and position by query, page, country, device and date
  • Any two periods side by side, with what appeared and vanished
  • The biggest winning and losing queries and pages in one call
  • What to work on first: striking-distance queries, low-CTR pages, decaying pages and competing pages, ranked by clicks at stake
  • Index status, last crawl and Google's chosen canonical for up to 20 URLs at a time
  • Submitted sitemaps with their errors and warnings
  • Queries where your own pages compete (Pro and Agency)
  • Google's ranking updates, to line up with your traffic
  • All 16 months of history Google keeps, on every plan, for year-over-year and seasonality
  • On paid plans, Bing Webmaster Tools too: queries, crawl errors, backlinks and submissions

The tools your AI gets

All through the same AskYourStack MCP address as your server tools. How to connect Google.

ToolWhat it doesPlan
gsc_performance_overviewClicks, impressions, CTR and position against the period before, with the biggest winning and losing queries and pagesEvery plan
gsc_opportunitiesWhat to work on first, ranked by clicks at stake: striking-distance queries, page-one pages with a low CTR, decaying pages and competing pagesEvery plan
gsc_search_analyticsPerformance by query, page, country, device or date, with filters and two-period comparisonsEvery plan
gsc_inspect_urlGoogle's own view of up to 20 URLs: indexed or not and why, last crawl, the canonical Google pickedEvery plan
gsc_sitemapsSubmitted sitemaps with errors, warnings and when Google last read themEvery plan
gsc_cannibalizationQueries where two or more of your pages split the impressions and compete with each otherSEO plans, Pro and up
google_updatesGoogle's core, spam and helpful content updates, to line up with traffic changesEvery plan
ga4_overviewSessions, users, engagement, conversions and revenue against the period before, by channel, with organic search's shareSEO plans, Pro and up
ga4_ai_trafficVisits from ChatGPT, Perplexity, Gemini, Claude, Copilot and other AI assistants, and the pages they land onSEO plans, Pro and up

Step by step for your AI client

Exactly where to click in Claude, ChatGPT, Cursor and Claude Code, which permissions Google shows, and how to pick your properties. Connect Google Search Console to Claude, ChatGPT or Cursor.

Have a server too?

Then your AI can check Google's numbers against what Googlebot really fetched. It matches Search Console's "Not found (404)" with the 404s in your access logs, "Google chose different canonical" with the canonical tags your shop outputs, and slow pages with the server's response time. Then it fixes the cause with your approval: redirects, robots.txt, canonicals, caching. Technical SEO with your AI.

Start with this prompt

Best for a drop or jump in traffic you want explained. With Google Analytics connected it also covers visits, conversions and AI-assistant traffic. Paste it into your AI with AskYourStack connected. It fetches the matching playbook and explains its plan before changing anything.

Using AskYourStack, find out why traffic to <domain> changed <recently / since date>. Start with gsc_properties and ga4_properties. Compare the last 28 days with the 28 before using gsc_performance_overview and ga4_overview, then drill down by page and query (gsc_search_analytics) and by landing page and channel (ga4_landing_pages). Check google_updates for core or spam updates rolling out at the time, and ga4_ai_traffic for visits from AI assistants. If it points at the site itself, check the server: crawl_report for errors served to Google, and core_web_vitals for the pages that lost the most. Tell me what changed, the evidence, and what you would do, before changing anything.

all prompts

Which plan

Search Console is on every plan, with all 16 months of history. Free: 1 property and 50 tool calls a day, no card and no server. Starter: 3 properties, all 16 months Google keeps. Pro: 10 properties, all 16 months Google keeps. Agency: 25 properties, all 16 months Google keeps. Pricing.

Questions

Can my AI change anything in Search Console?

No. AskYourStack asks only for Google's read-only Search Console permission. Submitting sitemaps, requesting indexing and removals stay with you in Search Console.

Is my Search Console data stored?

No. Your AI's request goes to Google and the answer goes back to your AI. AskYourStack logs that the call happened and how many rows came back, not the data.

Do I need a server?

No. Search Console works on its own, Free for one site or on an SEO plan. A server only adds the fixes.

What makes this different from other Search Console MCP servers?

All 16 months of history on every plan, Bing next to Google, a ranked list of what to work on first, and, if you connect a server, the fix: your AI can match Search Console's "Not found (404)" with the 404s Googlebot gets in your logs and repair the cause with your approval.

I manage clients' sites in other Google accounts.

Agency connects up to three Google accounts. Your AI reads each property through the account that can see it.

Google access is read-only: AskYourStack asks Google only for permission to view Search Console and Analytics data, and the data goes straight to your AI, not into our database. How Google data is handled · The SEO connector.

Connect your Search Console

Free for one site, with all 16 months of history. No card, no server, nothing to install.

Get started