MCP.Market

Google Search Console Connector MCP server

by malaysherasia-ai·io.github.malaysherasia-ai/google-search-console-connector·v0.1.3
No reviews yet

Google Search Console: search analytics, CSV reports, URL inspection, sitemaps, site verification.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

0 stars83 downloads/wk

Reviews

Write one

Nobody has reviewed Google Search Console Connector yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Google Search Console Connector tools (18, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • gsc_add_annotation

    Add a dated note to this project's performance chart, e.g. after deploying SEO changes ('Rewrote service page titles'). Shown in the dashboard so changes can be matched to traffic movements.

  • gsc_add_site

    Add a property to Search Console for the connected account. It stays unverified until gsc_verify_site succeeds.

  • gsc_connect

    Open the Connect page in the user's browser: Google Cloud setup, Google sign-in, and choosing this project's property. Waits until the user finishes (up to 10 minutes).

  • gsc_delete_sitemapwrite action

    Remove a sitemap from the property in Search Console (does not touch the file on the website).

  • gsc_disconnect

    Revoke this machine's Google access token and delete it locally.

  • gsc_export_report

    Download Search Console reports in one step: Dates, Queries, Pages, Countries, Devices, Search appearance, Query-page pairs and Sitemaps as CSV (same columns as Search Console's Export, plus previous-period comparison), report.json, and summary.md written for you to read next. Saved to .gsc-reports/ in the project (added to .gitignore).

  • gsc_get_verification_token

    Get the ownership verification token. META returns a <meta> tag for the site's <head> (URL-prefix properties). FILE returns an HTML file name/content to serve at the site root. DNS_TXT is required for sc-domain properties.

  • gsc_inspect_url

    URL Inspection: index status, coverage, last crawl, canonical and rich results for one URL in the property.

  • gsc_link_project

    Save which Search Console property this website project uses (writes .gsc-connect.json in the project root; contains no secrets).

  • gsc_list_sitemaps

    Sitemaps submitted for the property, with status, errors, warnings and last download time.

  • gsc_list_sites

    List Search Console properties the connected account can access, with permission level.

  • gsc_open_dashboard

    Open the local Search Console dashboard (performance, queries, pages, opportunities, indexing) in the user's browser.

  • gsc_performance_summary

    Totals for a period compared with the previous period of equal length, plus top queries and pages. A good first call for 'how is the site doing?'.

  • gsc_search_analytics

    Query Search Console performance data (clicks, impressions, CTR, position). Data is available for the last 16 months and usually lags 2–3 days. CTR is returned as a fraction.

  • gsc_set_brand_terms

    Set the words that make a query 'branded' (business name, product names, common misspellings). Enables branded vs non-branded analysis in gsc_search_analytics, reports and the dashboard.

  • gsc_status

    Show whether Google is connected, which account, and which property this project is linked to.

  • gsc_submit_sitemapwrite action

    Submit (or resubmit) a sitemap URL for the property.

  • gsc_verify_site

    Ask Google to check the verification token placed by the chosen method. Run after deploying the meta tag / file or adding the DNS record.

Public scan report

scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan19 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 8 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Google Search Console Connector compares

Against every graded SEO MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 88% of 769 SEO servers
Tools
18
the typical SEO server has 6
Tools that change things
11%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
83
more than 56% of 164 SEO servers with a package

What its tools let an agent do: 16 read · 2 change

Install Google Search Console Connector in Claude Code, Cursor or VS Code

Runs npx -y google-search-console-connector on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add google-search-console-connector -- npx -y google-search-console-connector
Add to Cursor

What the publisher says

From the Google Search Console Connector repository's README, as published. We do not edit it. Read it on GitHub

Google Search Console Connector for Claude Code

Connect any website project to Google Search Console from Claude Code, Google Antigravity or any MCP client. Sign in with your Google account once, then ask Claude about clicks, queries, rankings and indexing, pull every GSC report as CSV with one command, and track it all in a local SEO dashboard.

It's an open-source Search Console MCP server, a GSC report exporter and a dashboard, and it runs entirely on your computer. No Google Cloud setup, no API keys: you just sign in with Google.

If you find it useful, a ⭐ on GitHub helps other people find it.

Docs and updates: claude-repo.com/google-search-console-connector

Why this exists

If you build sites with an AI coding agent, getting Search Console data into it usually means logging in to search.google.com, clicking Export, downloading CSVs and dragging them into the chat. Every site, every time.

This tool removes those steps:

npx google-search-console-connector report

That one command downloads the same reports as Search Console's Export button (Dates, Queries, Pages, Countries, Devices, Search appearance) plus comparisons with the previous period, query-to-page pairs, sitemaps, and a summary.md written for Claude to read. Inside Claude Code you don't even type it. Ask "pull the Search Console report" and Claude runs the gscexportreport tool.

Features

  • Sign in with Google. One click in your browser, using Google's own OAuth 2.0 (PKCE). No Google Cloud project, API keys or passwords.
  • One-command GSC export. Pull CSV, JSON and Markdown reports for one site or all your sites (--all-sites), for any range up to 16 months.
  • MCP server for Claude Code and Antigravity. 18 tools: performance data, hourly data, branded vs non-branded queries, URL Inspection, sitemaps, adding properties and verifying ownership.
  • Local SEO dashboard. KPIs against the previous period, a trend chart (hourly, daily, weekly, monthly), queries, pages, countries, devices, sitemaps and URL Inspection. Light and dark themes.
  • Opportunities. Striking-distance keywords (positions 4–20), page-one pages with low CTR, and queries that are losing clicks.
  • Branded vs non-branded. Set your brand terms once; the dashboard, reports and Claude can all split traffic by them.
  • Chart notes. Claude can mark the chart when it ships SEO changes ("Rewrote service page titles"), so you can see what moved the numbers.
  • Site verification. Claude can add a new site to Search Console, put the verification meta tag in your code, and verify it after you deploy.
  • Current with Google. Supports the latest Search Console API features, including hourly data, Discover and Google News. A weekly check flags new API fields and Search Central announcements.
  • Private by default. Tokens and Search Console data stay on your machine and go only to Google. There is no server in between.

Quick start

You need Node.js 20 or newer and a Google account with access to Search Console.

1. Add it to Claude Code (once, for all your projects):

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

On Windows, wrap npx in cmd /c:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Google Search Console Connector: common questions

Is Google Search Console Connector MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Google Search Console Connector safety report
How do I install Google Search Console Connector?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Google Search Console Connector need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Google Search Console Connector maintained?
The last commit was 14 days ago (2026-10-19). The latest release is v0.1.3.
What can I use instead of Google Search Console Connector?
Servers from other publishers that do the same job: SEO Skill MCP server, Google Ads + Meta Ads + SEO/GEO MCP server and Google Search Console MCP server. Compare all Google Search Console Connector alternatives.
How does Google Search Console Connector compare with other SEO MCP servers?
safety score 92/100 (higher than 88% of 769 SEO servers); tools 18 (the typical SEO server has 6); tools that change things 11% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Google Search Console Connector

Same job from other publishers: the closest match first, then the best rated.

All Google Search Console Connector alternatives →