Search Console over MCP

Google Search Console over MCP, without running the server.

Connect your real Search Console to Claude Code, Cursor, or any coding agent in one line, and your agent gets the analysis, not raw JSON to sort out yourself.

Connect your site See the install

From $14.99/mo · works in Claude Code, Cursor, Cline & Windsurf

cursor
> connect google search console over mcp
QueryScope · connected · queryscope.dev · read-only
> what should I fix first?
QueryScope · fix this first
1 /pricing ranks #4, click rate below your curve 2 /docs/mcp position 11.3, one push to page 1 3 /changelog -54 clicks vs prior 28 days
A bare server hands your agent the rows. This hands it the call.

Built from the Search Console audit we run on our own SaaS, AppScreenshotStudio.

Two ways to do it

The open-source servers are good. The setup around them is the work.

There are several free Google Search Console MCP servers on GitHub, and they are worth it if you want to run your own. What you take on is a Google Cloud project, an OAuth screen to get verified for the restricted Search Console scope, a process to host, and an agent that receives raw rows. QueryScope is the hosted version of the same idea.

Run your own server

1create a Google Cloud project 2build an OAuth screen, submit for verification 3host the process, keep it running 4agent reads live GSC, wiped past 16 months 5output: raw rows to sort out yourself

Free, and yours to set up and maintain.

Connect QueryScope

> one line in your IDE, then authorize
✓no Cloud project or OAuth screen of your own ✓read-only grant you approve and can revoke ✓daily history kept past the 16-month wall ✓output: a ranked list of what to fix first

One line, hosted, and the analysis done.

Three things worth knowing before your agent reads a single row.

If any of the terminology is new, the Search Console glossary defines every metric and indexing state in a sentence, each with the caveat that makes it misleading.

01 The grant

It is read-only, and it is yours to revoke.

QueryScope reads your Search Console over the webmasters.readonly scope: clicks, impressions, position, per-page queries, indexing. It cannot change your site or your Search Console settings, and you can pull the grant in one click. Your agent gets read access to your data, nothing more.

scope: webmasters.readonly · you approve · you revoke

How the terminal read compares to the dashboard
02 The under-count

The query numbers are already short before your agent sees them.

Google hides rare queries for privacy, so the query table totals less than your real clicks, about half on average. A bare server passes that undercount straight through. QueryScope takes volume from the page level and treats the query list as intent, never as a total.

query total ≈ 53% of clicks · page total = 100%

Page-level vs query-level data
03 Where it stops

Your agent can pick the fix. It cannot promise the win.

QueryScope ranks which page to fix first and which move it needs. What it cannot see is the competing results page (so a climb is a bet, not a certainty) or anything past the click. It stops at the click: no revenue guess, no signups claim. The honest limit is the point.

reads: your GSC · blind to: the competition, the sale

The 16-month wall and kept history

One line in your IDE. Then authorize and pick a site.

install.sh 
claude mcp add --transport http queryscope https://mcp.queryscope.dev/mcp

Cursor, Cline, and Windsurf take the same URL in their MCP config. Your IDE runs the LLM, so there is no separate AI fee.

Point your coding agent at your own search data.

One price per site count. No credits, no metering. Connect over MCP in two minutes and keep the history Google throws away.

Connect your site See pricing

7-day free trial · $0 due today · cancel anytime in one click

FAQ

Google Search Console over MCP.

Isn't there a free open-source GSC MCP server?

Yes, several, and they are a fine choice if you want to run your own server. QueryScope is the hosted version: no Google Cloud project to set up, a daily snapshot kept past Google's 16-month window, and a ranked list of what to fix instead of raw rows. You are paying for the setup you skip and the analysis you get.

Do I need my own Google Cloud project or OAuth app?

No. You authorize QueryScope over a read-only Search Console grant you approve and can revoke. There is no consent screen of your own to build and submit for the restricted scope, which is the slowest part of running a server yourself.

Which coding agents and IDEs work?

Claude Code, Cursor, Cline, Windsurf, or any MCP client. You add one URL to the IDE's MCP config. Your IDE runs the LLM, so there is no separate AI fee.

Is it the same data as Search Console?

Yes, your own, read over an OAuth grant you approve and can revoke. Plus a daily snapshot kept past Google's 16-month window, so your history does not disappear.

What can my agent actually do with it?

Read your clicks, impressions, position, per-page query intent, and indexing, and get a ranked list of what to fix first, tagged with the move it needs. It stops at the click: it will not guess your revenue and it will not touch your site.