Google Search Console MCP for Claude and ChatGPT

Google Search Console MCP is a connector built on the Model Context Protocol (MCP), the open standard Anthropic introduced in 2024, that lets an AI assistant like Claude read your Search Console data. Instead of filtering the Performance report and exporting spreadsheets, you ask questions in plain English and Claude answers from your live queries, pages, clicks, impressions, CTR and positions.

No. Google publishes official MCP servers for Google Ads and Google Analytics, but not for Search Console. Every Search Console MCP is built by a third party on top of the official Search Console API: community open-source servers you install and run yourself, or managed options like GrowthSpree's, which connects with Google sign-in.

You can start free. The Basic plan covers Google Ads, Google Analytics, Search Console, LinkedIn Ads, Microsoft Advertising and HubSpot, used inside the AI tool you already have. Premium adds Meta Ads, the GrowthSpree web chat and Slack.

No. You connect Search Console with Google sign-in and GrowthSpree generates your personal API key. There is no Google Cloud project, no API credentials file and no Python or Node to install.

On Claude's free plan, use the Claude Desktop extension. On a paid Claude plan or Cowork, add GrowthSpree as a custom connector. Developers can connect Claude Code with one command. For Cursor, Windsurf, ChatGPT and other MCP clients, paste the server config with your API key. Every option uses the same token from your dashboard.

About 5 minutes: enter your work email to get your login, connect Search Console and copy your token, add GrowthSpree to your AI tool (Claude Desktop extension, Claude connector, one Claude Code command or an MCP config), then ask your first question.

The connection is built for reading Search Console data so Claude can analyse it. It cannot edit your website or robots.txt; when Claude recommends a fix, you or your developer make it.

Restricted or full user access to a Search Console property is enough to connect it and read its performance data.

Yes. You choose the site when you connect, domain or URL-prefix property, and then set which connected site each conversation uses. That keeps multi-brand and agency work separate.

Yes. Because Claude can see which queries a page ranks for, its position and its CTR, it writes titles and meta descriptions aimed at the queries that matter, content briefs for keywords you almost rank for, and refresh plans for pages that are slipping.

Yes. Connect GrowthSpree's Google Ads and Google Analytics MCPs too, and Claude can find paid keywords you already rank for organically, and check whether organic visitors engage and convert once they land.

Claude reads the same data the Search Console API provides: up to 16 months of queries, pages, countries, devices, clicks, impressions, CTR and average position. Like the Search Console interface, some rare or anonymised queries are not reported.

The Search Console API is the interface developers write code against. An MCP server wraps that API as tools an AI assistant can call on its own, so Claude decides which reports to run, pulls the data and explains the results without you writing code.

Yes. GrowthSpree's MCP server is hosted, so it works with any client that accepts a remote MCP server: add it to ChatGPT as a custom connector, or paste the config into Cursor, Windsurf and other MCP clients. Claude has the most setup options: the Desktop extension on the free plan, a custom connector on paid plans and Cowork, and one command in Claude Code.

GrowthSpree uses your data to answer your questions and run the reports you set up. How it is stored and processed is set out in our privacy policy and your agreement with GrowthSpree. The AI assistant you choose, such as Claude or ChatGPT, also applies its own data policy.

A generic connector only gives an AI tool access to your data, which is quickly becoming a commodity. GrowthSpree adds what decides the quality of the answer: benchmarks from 99 audited B2B SaaS accounts, prompts and playbooks from $60M+ of managed B2B ad spend, every B2B channel plus HubSpot on one account, and workflow features such as company context, saved prompts, scheduled audits and a Slack bot.

The paid search benchmarks come from GrowthSpree's $11.3M Google Ads Waste Report, an analysis of 43 B2B SaaS accounts. They show where paid search money is wasted, which is often traffic SEO can win instead. The report is free to read on the GrowthSpree website.

Because B2B companies, SaaS or not, are measured on pipeline, not online sales. GrowthSpree connects Search Console with LinkedIn Ads, Microsoft Advertising and HubSpot on one account, and its prompts look at demo and quote requests, SQLs, assisted conversions and 90-day windows that match B2B sales cycles.

Yes. Set your company context once, including what you sell, your ICP, goals and brand voice, and it is applied to every conversation so recommendations and copy fit your business.

Yes. Each teammate gets their own login and API key, and you can share any conversation through a private link. On Premium, the Slack bot answers questions for the whole team in your channels.

No. On Claude's free plan you install the GrowthSpree extension (.MCPB file) in Claude Desktop and paste your token. On paid Claude plans and Claude Cowork you can add it as a custom connector instead, which also gives you higher usage limits for large properties and long reports.

B2B and B2B SaaS marketing leaders, SEO and content teams, agencies reporting across many client sites, and founders who want to know how organic search is doing. That includes software companies and B2B firms in IT services, professional services and manufacturing.