gsc-connector

Search Console Connector · free · open source · runs on your machine

Google Search Console, inside Claude Code.

Sign in with Google once. Then ask Claude Code or Antigravity about your clicks, queries and rankings, pull every Search Console report as CSV with one command, and track it all in a dashboard that runs on your own computer.

$ claude mcp add gsc --scope user -- npx -y google-search-console-connector@latest

On Windows, put cmd /c before npx. Then open Claude Code in a website's folder and say “Connect this project to Google Search Console”.

The gsc-connector dashboard: total clicks, impressions, CTR and average position against the previous period, a daily clicks chart with notes, and top queries and pages
The local dashboard, shown with sample data.

Connect in three steps.

Install, sign in with Google, pick the site. Shown with sample data. Click to pause.
  1. Install

    One command adds the connector to Claude Code. It works with Antigravity and other MCP clients too.

  2. Sign in with Google

    A page opens on your computer. Choose whether to share anonymous usage, then sign in with the account that has your Search Console access. On Google’s screen, tick the Search Console box before you click Continue.

  3. Pick the site

    Choose which Search Console property belongs to the project. Claude uses it from then on.

What Google shows you: choose your account, then tick the Search Console box. No “unverified app” warning.

Ask Claude about your search data.

  • How did the site do in the last 28 days?
  • Pull the Search Console report for the last 3 months.
  • Which queries are we ranking 4 to 20 for?
  • Inspect /services/ and tell me why it isn't indexed.
  • Submit the sitemap and note that we launched the new pages.
  • Open the Search Console dashboard.

What gsc-connector does.

One-command reports

Dates, queries, pages, countries, devices and search appearance as CSV, with previous-period columns, query-page pairs and a summary written for Claude to read.

18 tools for your agent

Performance data including hourly, URL Inspection, sitemaps, adding and verifying sites, chart notes, branded vs non-branded queries.

A local dashboard

KPIs against the previous period, trends from 24 hours to 16 months, queries, pages, countries, devices, sitemaps and inspection.

Opportunities

Keywords in striking distance, page-one pages with low click-through, and queries that are losing clicks.

Every site you manage

Each project folder links to its own property, and one command exports every property you can access.

Current with Google

Hourly data, Discover and Google News, weekly and monthly views. A weekly check flags new Search Console API features.

What Google data it uses.

The connector runs on your computer. When you sign in, Google asks you to allow the following, and nothing more:

Google permissionWhat the connector uses it for
View and manage Search Console dataShowing your performance data, inspecting URLs, listing and submitting sitemaps, and adding your sites as properties, when you ask.
Your email addressShowing which Google account is connected.
Verify site ownership (asked only when needed)Getting the verification tag for a new site you own and confirming it with Google, when you ask Claude to verify a site.
  • Your Google tokens are stored on your computer, and your Search Console data goes only between your computer and Google. There is no server of ours in between.
  • We never receive your sites, URLs, queries, metrics or email address, so there is nothing for us to sell or share.
  • Usage metrics are optional. If you say yes, anonymous event names go to Google Analytics, never Search Console data. If you say no, nothing is sent.
  • You can disconnect in the dashboard at any time, or revoke access at myaccount.google.com/permissions.

The numbers, as GitHub counts them.

Stars from the repository, clones from GitHub's traffic API. Baked into this page once a day, then checked every minute while you have it open. When nothing changed, nothing moves.

0
stars
193
clones · all time
since 8 Oct, counted daily
193
clones · last 14 days
+47 vs the week before
103
unique cloners · 14 days

snapshotsource: github.com/malaysherasia-ai/google-search-console-connector-for-claude-code

Questions about gsc-connector.

Do I need a Google Cloud account?

No. You sign in with the Google account you already use for Search Console. Using your own Google Cloud project is an optional advanced setting for agencies and developers.

Is the Google Search Console API free?

Yes. Google charges nothing for the Search Console API, and the connector is free and MIT licensed.

Who can see my Search Console data?

Only you and Google. The connector runs on your computer; tokens and data never pass through a server of ours.

Can I export more than 1,000 rows?

Yes. Search Console's own export stops at 1,000 rows. The connector pages through the API up to Google's limit of 50,000 rows per day per search type.

Does it work with Antigravity and other MCP clients?

Yes. Any MCP client that can start a local server works, including Claude Code, Google Antigravity and Cursor. There is also a command-line tool.

Why might Google say the app isn't verified?

Google reviews every new app that asks for Search Console access. Until that review finishes, Google shows a notice; choose Advanced, then Go to Search Console Connector.