ScopeMCP
Get started

Turn your search data into your next SEO move.

Read-only Search Console over MCP: performance by any dimension, period comparison, evidence-based opportunities, URL inspection and sitemap health.

Get startedConnect ClaudeTool reference

Seven tools covering the whole Search Console surface. Every report names the window it searched and the limits of what those numbers can support, so your assistant quotes the caveat along with the finding.

Default window
28 completed days
Ending three days ago, with the mirrored previous window for comparison.
Dimensions
7
Date, query, page, country, device, search appearance — and combinations of two.
Filters
10 per call
ANDed together, so filters narrow rather than widen.

Tools

7 tools on this source

gsc_get_performance

Read performance

Clicks, impressions, CTR and position by query, page, country, device, date or search appearance. Optional daily series and previous-period totals.

gsc_compare_performance

Compare two windows

Row-level differences between an explicit current and baseline window, with largest gains and largest declines separated out.

gsc_get_opportunities

Find opportunities

Striking distance, high-impression low-CTR, page-2 queries, declines and possible cannibalisation — each with the numbers that produced it.

gsc_inspect_url

Inspect one URL

Index verdict, coverage state, canonical selection, crawl timestamps, robots state, mobile usability and AMP.

gsc_inspect_urls

Inspect up to ten

The same inspection batched for URLs you already know, issued sequentially to stay inside the per-property quota.

gsc_get_sitemaps

List sitemaps

Submitted sitemaps with processing state, warnings, errors and indexed counts, plus a plain-language health summary.

gsc_get_sitemap

Inspect one sitemap

Detailed status and content counts for a single named sitemap.

Connect your assistant

Pick the agent you already use

CL

Claude

Add a custom connector in Settings. Claude can then use every ScopeMCP tool in the conversation.

CH

ChatGPT

Install ScopeMCP as a custom app so it appears in your Apps & connectors list.

CO

Codex

Add the endpoint to your session configuration and query it alongside your repo tools.

CL

Claude Code

Register the endpoint in your project so it works in the terminal, in CI and in review sessions.

Before you start

What you need, and what you will not get

Requirements

  • The Search Console API and URL Inspection API enabled in your Google Cloud project.
  • A Search Console property your connected Google account can actually read.
  • Read-only OAuth consent. ScopeMCP cannot write to your property.

Boundaries

The limits worth knowing before you trust an answer.

  • Data lags roughly three days, so windows end three days ago by default.
  • URL inspection reports Google’s stored state, not a live crawl. It will not reflect a change you made five minutes ago.
  • Row caps mean returned totals are a floor when the result set is truncated. The report says so.
  • A low CTR is only actionable if the ranking itself is right for the query.

Endpoint

remote MCP endpoint
${env.appUrl}/mcp

Discovery metadata is served at /.well-known/mcp.json, so a client that supports it finds the endpoint from the domain alone.