MCP for Google Search Console

Search Console, inside your AI Agent.

Analyze performance, explore queries, and inspect URLs. All from the AI assistant you already use.

Not published yet. Commands require a confirmed published release.

bunx --bun @sonnivasquez/gsc-mcp@latest setup
Read the setup guideExplore use cases
  • 29 tools
  • Read-only by default
  • Runs locally
  • Provider-visible results

Works with the tools you already use

Use cases

Your Search Console data. Put to work.

Go from a question to evidence, inside the assistant you already use.

Performance

Understand what changed. And where.

Compare clicks and impressions across periods. Trace a traffic change to the pages and searches behind it.

Each comparison returns its date window and coverage; an overlapping update is timing only, never proof of cause.

Explore traffic changes
CodexIllustrative example

Compare the last 28 days with the previous period for sc-domain:example.com.

Clicks increased in this sample. Compare impressions and CTR to see what changed.

gsc_compare_periods
Illustrative performance response with sample data, not a live query.
MetricCurrentPreviousChange
Clicks12,54010,200+22.9%
Impressions245,231210,400+16.6%
CTR5.11%4.85%+0.26 pp

URL inspection

See your URL through Google's eyes.

Check the indexing state Google reports, along with coverage and sitemap information. Start an audit with evidence you can inspect.

Shows Google's reported status; inspecting a URL does not request or guarantee indexing.

Explore URL inspection
ClaudeIllustrative example

Is https://example.com/guide indexed? Check it for sc-domain:example.com.

Google reports this sample URL as submitted and indexed. Here is the reported evidence.

gsc_inspect_urls
Illustrative url inspection response with sample data, not a live query.
FieldReported value
URLhttps://example.com/guide
VerdictPASS
CoverageSubmitted and indexed
Canonicalhttps://example.com/guide

Queries & pages

Find the searches you can build on.

Discover queries with impressions but few clicks. Connect them to your pages and decide where to improve content.

Position is an impression-weighted average, not a rank tracker — read it as direction, not rank.

Explore search opportunities
CursorIllustrative example

Find high-impression, low-CTR queries for sc-domain:example.com over the last 28 days.

These sample queries have visibility but few clicks. They are starting points for a content review.

gsc_search_analytics
Illustrative queries & pages response with sample data, not a live query.
QueryClicksImpressionsCTRPosition
seo checklist1248,4201.5%8.2
technical seo866,1501.4%11.4
indexing guide573,8001.5%9.6
search analytics422,9101.4%12.3

Automation · full access

Submit your sitemap. Keep publishing moving.

Let your assistant notify Search Console about an updated sitemap. Enable full access only when you want it to make changes.

Sitemap submission requires full access and property permissions. It does not guarantee crawling or indexing.

Review write permissions
CodexIllustrative example

With full access enabled, submit https://example.com/sitemap.xml for sc-domain:example.com.

This sample shows a successful sitemap submission. Full access and property permissions are required; indexing is not guaranteed.

gsc_submit_sitemap
Illustrative automation · full access response with sample data, not a live query.
FieldSample response
siteUrlsc-domain:example.com
sitemapUrlhttps://example.com/sitemap.xml
successtrue
errornull

Sitemaps

Know what Google sees in your sitemaps.

List the sitemaps registered for your property. Check their reported errors and warnings before investigating individual URLs.

Listing sitemaps is read-only. A submitted sitemap is not proof that its pages are indexed.

Explore sitemaps
CursorIllustrative example

List the registered sitemaps, errors, and warnings for sc-domain:example.com.

One sample sitemap has a warning. Inspect its details before making changes.

gsc_list_sitemaps
Illustrative sitemaps response with sample data, not a live query.
SitemapErrorsWarnings
/sitemap.xml00
/sitemap-posts.xml01
/sitemap-pages.xml00

Reporting

Turn the week's data into a useful report.

Bring totals, movers, and opportunities into a Markdown report. Review its coverage and limitations before sharing it.

Server-generated Markdown export with a limitations section. Review the returned coverage before using it.

Explore weekly reports
CodexIllustrative example

Create a weekly report for sc-domain:example.com and include the limitations.

This sample weekly report organizes the evidence into four sections.

gsc_generate_report
Illustrative reporting response with sample data, not a live query.
Report sectionContents
OverviewTotals and period comparison
MoversPage and query changes
OpportunitiesQueries to investigate
LimitationsCoverage and date window

Examples use sample data for example.com. Your assistant returns the evidence for your own property.

Tools

One MCP. Your Search Console toolkit.

Four ways to put your Search Console data to work.

Explore all tools

Performance

Compare clicks, impressions and CTR to understand what changed.

Search opportunities

Find searches and pages with room to grow.

URL indexing

Check whether a page is indexed and investigate issues.

Sitemaps

Review your submitted sitemaps and spot errors or warnings.

See a question become evidence.

Choose a question and explore a sample answer from your agent.

Illustrative data for example.com. This demo makes no Google or AI calls.

Sample conversation
You

Did my traffic really drop — or just move?

CodexSample answer

Clicks increased in this sample. Compare impressions and CTR to see what changed.

gsc_compare_periodsExample tool result
Illustrative performance data for example.com, not a live query.
MetricCurrentPreviousChange
Clicks12,54010,200+22.9%
Impressions245,231210,400+16.6%
CTR5.11%4.85%+0.26 pp

Each comparison returns its date window and coverage; an overlapping update is timing only, never proof of cause.

Paste this question into your agent, then replace the example property with yours.

Local by design

Your machine. Your credentials. Your choice.

Connect locally, with permissions you control.

Credentials stay local

Tokens stay in ~/.gsc-mcp/ on your machine. This website never runs your queries or collects credentials.

Start with read-only

Quick Connect is read-only. Write operations require explicit full access and your own OAuth client or service account.

Know where answers go

Your MCP client and its AI provider see the tool results used to answer your questions.

Read the privacy details
Set up your local connectionRuntime, credentials, client configuration, and verification

One command, once the release is live.

Not published yet. The commands below run only after release @sonnivasquez/gsc-mcp@0.1.0 is confirmed published. Until then there is no public install path, and this page does not establish registry availability.

verify with bun --version

Setup — pinned to @sonnivasquez/gsc-mcp@0.1.0

bunx --bun @sonnivasquez/gsc-mcp@0.1.0 setup

  1. STEP 1 OF 4

    Check the runtime

    Bun 1 or newer, or Node 22 or newer — plus a Google account that can open at least one Search Console property.

  2. STEP 2 OF 4

    Create the Google credential

    Quick Connect signs in with no Cloud setup and stays read-only; full access needs your own Desktop OAuth client or a service account.

    Choose a credential →

  3. STEP 3 OF 4

    Connect your client

    Desktop and Cursor merge one gsc entry into the config file with a timestamped backup; Code and Codex print the exact command; print never writes.

    Connect a client →

  4. STEP 4 OF 4

    Verify before you ask

    doctor checks runtime, paths, and auth state offline; auth status --online validates against Google with no secrets printed.

    Read the command reference →

Verify — same runtime

bunx --bun @sonnivasquez/gsc-mcp@0.1.0 doctor
bunx --bun @sonnivasquez/gsc-mcp@0.1.0 auth status --online

Questions before you connect.

Short answers from the docs. Longer versions live in the setup guide.

What is gsc-mcp?

A local MCP server that connects your Search Console data to the AI assistant you already use. It runs on your machine and talks to your assistant's client over a local connection — this website never runs your queries.

Which assistants can I connect?

Claude Desktop, Claude Code, Cursor, or Codex, and any other client that connects to a local MCP server. See client setup for the exact steps per client.

Do I need Google credentials?

You need a Google account with access to your Search Console property. Quick Connect uses Google sign-in for read-only access. Full access requires your own OAuth client or service account. Follow the credentials guide for your chosen connection.

Is gsc-mcp free?

The code is open source under Apache-2.0, with no gsc-mcp subscription. Your AI client or provider may charge separately. The package does not yet have a confirmed public release.

What permissions does it request?

Read-only access is the default: it can read Search Console data and inspect URLs. Full access also enables sitemap changes and eligible Indexing API notifications. It does not request Gmail, Drive, or Analytics access. Review access modes and permissions before enabling writes.

Do credentials stay local?

Yes. Tokens stay in ~/.gsc-mcp/ on your machine. Your MCP client and its AI provider see the tool results used to answer your questions — local means no backend of ours, not invisible answers.

Does inspecting a URL guarantee indexing?

No. The server reports Google's indexing state for a URL and the property sitemaps that include it. Inspecting a URL does not request indexing and never guarantees it.

Is the package published?

Not yet. @sonnivasquez/gsc-mcp@0.1.0 has no confirmed published release, so there is no public install path — the commands on this page run only after a release is confirmed published. Maintained by Sonni Vasquez (sonnivasquez.com).

Bring Search Console into your AI workflow.

Read the guide, connect locally, and start with a question.

Get startedGitHub