Google Search Console MCP

Name: Google Search Console MCP
Author: sonnivasquez

by sonnivasquezversion 1.1.0i★ –iRuns on your computer

Registry nameio.github.sonnivasquez/gsc-mcp

Install

Overview

Description from the maker (original English)

Local, read-only Google Search Console MCP server. Quick Connect needs no Cloud project.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory
You need to fill in: GSC_OAUTH_CLIENT_SECRET

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: GSC_AUTH_MODE, GSC_ACCESS_MODE, GSC_SITE_URLS, GSC_KEY_FILE, GSC_DATA_DIR, GSC_EXPORTS, GSC_HISTORY, GSC_OAUTH_SECRETS_FILE, GSC_OAUTH_CLIENT_ID, GSC_OAUTH_CLIENT_SECRET, GSC_SCOPES, GSC_ENABLE_WRITE

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "gsc": {
      "command": "npx",
      "args": [
        "-y",
        "@sonnivasquez/gsc-mcp"
      ],
      "env": {
        "GSC_AUTH_MODE": "your-value",
        "GSC_ACCESS_MODE": "your-value",
        "GSC_SITE_URLS": "your-value",
        "GSC_KEY_FILE": "your-value",
        "GSC_DATA_DIR": "your-value",
        "GSC_EXPORTS": "your-value",
        "GSC_HISTORY": "your-value",
        "GSC_OAUTH_SECRETS_FILE": "your-value",
        "GSC_OAUTH_CLIENT_ID": "your-value",
        "GSC_OAUTH_CLIENT_SECRET": "your-value",
        "GSC_SCOPES": "your-value",
        "GSC_ENABLE_WRITE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add gsc --env GSC_AUTH_MODE=your-value --env GSC_ACCESS_MODE=your-value --env GSC_SITE_URLS=your-value --env GSC_KEY_FILE=your-value --env GSC_DATA_DIR=your-value --env GSC_EXPORTS=your-value --env GSC_HISTORY=your-value --env GSC_OAUTH_SECRETS_FILE=your-value --env GSC_OAUTH_CLIENT_ID=your-value --env GSC_OAUTH_CLIENT_SECRET=your-value --env GSC_SCOPES=your-value --env GSC_ENABLE_WRITE=your-value -- npx -y @sonnivasquez/gsc-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "gsc": {
      "command": "npx",
      "args": [
        "-y",
        "@sonnivasquez/gsc-mcp"
      ],
      "env": {
        "GSC_AUTH_MODE": "your-value",
        "GSC_ACCESS_MODE": "your-value",
        "GSC_SITE_URLS": "your-value",
        "GSC_KEY_FILE": "your-value",
        "GSC_DATA_DIR": "your-value",
        "GSC_EXPORTS": "your-value",
        "GSC_HISTORY": "your-value",
        "GSC_OAUTH_SECRETS_FILE": "your-value",
        "GSC_OAUTH_CLIENT_ID": "your-value",
        "GSC_OAUTH_CLIENT_SECRET": "your-value",
        "GSC_SCOPES": "your-value",
        "GSC_ENABLE_WRITE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "gsc": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@sonnivasquez/gsc-mcp"
      ],
      "env": {
        "GSC_AUTH_MODE": "your-value",
        "GSC_ACCESS_MODE": "your-value",
        "GSC_SITE_URLS": "your-value",
        "GSC_KEY_FILE": "your-value",
        "GSC_DATA_DIR": "your-value",
        "GSC_EXPORTS": "your-value",
        "GSC_HISTORY": "your-value",
        "GSC_OAUTH_SECRETS_FILE": "your-value",
        "GSC_OAUTH_CLIENT_ID": "your-value",
        "GSC_OAUTH_CLIENT_SECRET": "your-value",
        "GSC_SCOPES": "your-value",
        "GSC_ENABLE_WRITE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

GSC_AUTH_MODE env
oauth or service_account. Unset defaults to service_account. Set oauth for Quick Connect or your own OAuth client.
GSC_ACCESS_MODE env
readonly or full. full enables gsc_submit_url, gsc_submit_batch, and gsc_submit_sitemap. When unset, legacy GSC_SCOPES and GSC_ENABLE_WRITE apply and writes stay off unless both allow them. Setup ref…
GSC_SITE_URLS env
Property allowlist. JSON string array of exact Search Console property ids, a legacy comma-separated list, or all alone (or JSON ["all"]) for every current and future property. Property-scoped tools…
GSC_KEY_FILE env
Path to a service account JSON key. Required when GSC_AUTH_MODE is service_account, which is the default mode.
GSC_DATA_DIR env
Local state directory for OAuth tokens, datasets and opt-in audit history. Default is ~/.gsc-mcp.
GSC_EXPORTS env
Set to 1 to allow gsc_export_dataset and saved gsc_generate_report files on this machine. Any other value keeps local export disabled.
GSC_HISTORY env
Set to 1 for explicit local gsc_change_impact history actions. Independent of exports; no scheduler or notifications.
GSC_OAUTH_SECRETS_FILE env
Optional path to a Desktop OAuth client secrets JSON file. It takes precedence over GSC_OAUTH_CLIENT_ID and GSC_OAUTH_CLIENT_SECRET. Quick Connect does not need it.
GSC_OAUTH_CLIENT_ID env
Optional OAuth client id. Used with GSC_OAUTH_CLIENT_SECRET when GSC_OAUTH_SECRETS_FILE is unset. Quick Connect does not need it.
GSC_OAUTH_CLIENT_SECRET secret env
Optional OAuth client secret paired with GSC_OAUTH_CLIENT_ID. Quick Connect does not need it.
GSC_SCOPES env
Legacy scope tier, readonly or full. Ignored when GSC_ACCESS_MODE is set. full alone does not enable writes.
GSC_ENABLE_WRITE env
Legacy write opt-in. Set to 1 together with GSC_SCOPES=full when GSC_ACCESS_MODE is unset. Ignored when GSC_ACCESS_MODE is set.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account sonnivasquez, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 5675 servers in this category
Published to the registry more recently than 93% of the other 5675 servers in this category
Basic checks equal to or better than 100% of the other 5675 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Google Search Console MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: GSC_OAUTH_CLIENT_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.1.0) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 2 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Google Search Console MCP server

A local Google Search Console MCP server to compare search performance, find SEO opportunities, and check URL indexing status from your AI assistant using your own Google Search Console data.

GSC MCP is an open-source MCP server by Sonni Vasquez. It runs locally over stdio with Node.js or Bun and provides 34 tools. Google API requests run from your machine, with read-only Google access by default and access limited to the properties you select.

Website · npm package · Quickstart · Guía en español · Tool catalog

This is an independent project, not an official Google product.

Install with npx

The buttons and snippets below start the local stdio server with npx -y @sonnivasquez/gsc-mcp. They set GSC_AUTH_MODE=oauth and GSC_ACCESS_MODE=readonly. They do not sign you in to Google and they do not choose a property. Node.js 22 or newer is required. After the client starts the server, set GSC_SITE_URLS to your Search Console property and run gsc auth login or gsc setup. Quick Connect uses the shared read-only OAuth client shipped in this package, so you do not create a Google Cloud project for that path.

Claude Code

Replace sc-domain:example.com with your Search Console property id:

claude mcp add gsc-mcp -e GSC_AUTH_MODE=oauth -e GSC_ACCESS_MODE=readonly -e GSC_SITE_URLS=sc-domain:example.com -- npx -y @sonnivasquez/gsc-mcp

JSON config

Same command, for a client that reads mcpServers. Replace the example property:

"mcpServers": { "gsc-mcp": { "command": "npx", "args": ["-y", "@sonnivasquez/gsc-mcp"], "env": { "GSC_AUTH_MODE": "oauth", "GSC_ACCESS_MODE": "readonly", "GSC_SITE_URLS": "sc-domain:example.com" } } } }

Why this one

Quick Connect is the path that skips creating a Google Cloud OAuth client. Custom OAuth and service accounts in this same server still use credentials you create. Both paths run locally.

	Quick Connect in this server	Your own Google credentials
Google Cloud project	Not required. This package ships a shared read-only OAuth client.	Custom OAuth needs your client (`GSC_OAUTH_SECRETS_FILE`, or `GSC_OAUTH_CLIENT_ID` plus `GSC_OAUTH_CLIENT_SECRET`). A service account needs `GSC_KEY_FILE`.
Where it runs	Local stdio process. Google API requests run from your machine.	Same local process.
Default access	Read-only. Setup refuses full access for Quick Connect.	Read-only unless `GSC_ACCESS_MODE=full`. That mode enables `gsc_submit_url`, `gsc_submit_batch`, and `gsc_submit_sitemap`.
Tools	34 `gsc_*` tools registered by the server.	The same 34 tools.
Also registered here	`gsc_genai_conversation_queries`, `gsc_check_update_impact`, and `gsc_image_page_audit`.	The same tools.

gsc_genai_conversation_queries reads AI-conversation exhaust in query data. gsc_check_update_impact compares a drop window with confirmed ranking updates and reports temporal coincidence only. gsc_image_page_audit fetches your own pages and their image bytes.

What you can do

SEO task	What GSC MCP returns	Example tools
Understand a traffic change	Clicks, impressions, CTR, average position and period comparisons by page or query	`gsc_performance_overview`, `gsc_compare_periods`, `gsc_analyze_traffic_drop`
Prioritize pages and queries	Candidates with low CTR, weak positions or declining traffic, using explicit thresholds	`gsc_find_opportunities`, `gsc_content_decay`
Review competing pages	Queries served by multiple pages on your site, with evidence for editorial review	`gsc_detect_cannibalization`, `gsc_query_pages`
Inspect indexing and sitemaps	Google's indexed view of selected URLs and registered sitemap states	`gsc_inspect_urls`, `gsc_list_sitemaps`
Compare segments	Brand terms, site folders, countries, devices, or web versus image search	`gsc_analyze_segments`, `gsc_compare_web_image`
Audit on-page images	Findings from downloading your own pages and their referenced images	`gsc_image_page_audit`
Audit a page or an index sample	Current HTTP HTML and exact-page queries, or indexed-view inspection from sitemap discovery	`gsc_page_audit`, `gsc_indexing_audit`
Review internal links	Bounded HTML link graph and literal suggestions	`gsc_internal_link_audit`
Evaluate changes or a migration	Observed before/after metrics and declared URL mappings	`gsc_change_impact`, `gsc_migration_audit`
Prepare reports	Markdown reports and optional local dataset exports	`gsc_generate_report`, `gsc_export_dataset`

These are analysis tools. Opportunity and cannibalization results are candidates to review, not proof that a particular SEO change will improve rankings.

Get started

You need Node.js 22 or newer, npm or Bun, and a Google account with access to a Search Console property. Bun can install the package and run the MCP server; the global gsc CLI still requires Node.js.

npm install -g @sonnivasquez/gsc-mcp

gsc setup

Setup guides you through:

Sign in to Google. Choose read-only Quick Connect, or use your own OAuth client or a service account.
Choose properties. Select the Search Console properties this server may access.
Connect your client. Review and approve the configuration preview. Setup preserves other MCP servers.

Quick Connect uses a shared Desktop OAuth application and needs no Google Cloud project setup. Complete Google sign-in in your browser. Never paste passwords, OAuth credentials or tokens into an AI chat.

Check your local installation and saved authentication state:

gsc doctor

gsc auth status

To check access with a minimal request to Google, run gsc auth status --online. Restart your MCP client if the tools do not appear.

Other installation options

With Bun as the package manager:

bun install -g @sonnivasquez/gsc-mcp

gsc setup

The shell installer installs the latest package globally and opens setup. It uses npm by default and does not use sudo:

curl -fsSL https://gscmcp.dev/install.sh | sh

To use Bun with the installer:

curl -fsSL https://gscmcp.dev/install.sh | sh -s -- --manager bun

Read the installer or follow the quickstart for details.

Supported clients

Guided setup supports Claude Desktop, Claude Code, Cursor, Codex, OpenCode and Pi. It can also print JSON for another compatible MCP client. GSC MCP uses local stdio, so the client must support launching a local server.

See client setup instructions. Use gsc setup --dry-run to preview changes or gsc setup --verbose for configuration details. OpenCode and Pi configuration is global.

Install with your AI agent

Copy this prompt into an agent that can run terminal commands. You complete Google sign-in yourself:

Install @sonnivasquez/gsc-mcp globally with npm, or Bun if I prefer, then run gsc setup.

Use read-only Quick Connect. Help me sign in to Google, choose my Search Console properties and connect my MCP client while preserving other MCP servers. Never ask me to paste credentials or tokens into chat. Verify with gsc doctor and tell me whether I need to restart my client. Do not query Search Console until I ask.

Try it with your site

After setup, ask your assistant to list the properties it can access. Use an exact property identifier such as sc-domain:example.com or https://example.com/ in subsequent requests.

The prompts below are examples, not measured results:

For sc-domain:example.com, compare the last 28 days with the previous period.

Show the pages with the largest observed click losses, including impressions, CTR and average position. State the dates and coverage of the returned data.

Find queries for sc-domain:example.com with at least 500 impressions and CTR

below 2% in the last 28 days. Show their ranking pages and prioritize candidates for a title and snippet review. Do not edit the site.

Inspect these three URLs on my selected property and show Google's indexed

status for each. Then list its registered sitemaps. Do not submit anything.

You can also ask for pages with sustained traffic declines, query overlap across your own pages, brand versus non-brand segments, or a Markdown performance report. Saving reports and exporting datasets require GSC_EXPORTS=1 in your MCP client's server environment. Restart the client after changing that environment.

On-demand website audits and change history

Version 1.1.0 adds gsc_page_audit, gsc_indexing_audit, gsc_internal_link_audit, gsc_change_impact, and gsc_migration_audit. They combine bounded HTTP HTML or sitemap reads with your own GSC data. They do not render JavaScript or run in the background; client-rendered content and links remain unknown. Continue batches explicitly using nextCursor; sessions expire after 15 idle minutes.

GSC_HISTORY=1 enables explicit local change records and saved measurements, independently of GSC_EXPORTS. Transient before/after analysis needs no history. Results may be partial even when the scheduled work completes: check status, coverage and warnings. Full evidence may require gsc_get_dataset. No alerts service, scheduler or automatic captures are installed. See audit inputs, limits, evidence pagination and examples. These audits require version 1.1.0 or later. Check gsc_capabilities in the running server after updating and restarting your MCP client.

Authentication and access

Connection	Requirements	Access
Quick Connect	Browser sign-in with a Google account that can access the property	Read-only, using the shared OAuth application
Custom OAuth	Your own Google Cloud OAuth client and browser sign-in	Read-only, or full access after explicit configuration
Service account	Your own credentials file and permissions for the property	Read-only, or full access after explicit configuration

Read-only access blocks Google wr

Only the beginning is shown; read the rest in the repo

Google Search Console MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Google Search Console MCP server

Install with npx

Claude Code

JSON config

Why this one

What you can do

Get started

Other installation options

Supported clients

Install with your AI agent

Try it with your site

On-demand website audits and change history

Authentication and access