How do I install Gsc?

Gsc is a remote plugin. You do not need to install anything locally. Add the server URL to your AI app's MCP configuration and you are ready to go.

Yes. Gsc passed MCP Marketplace's automated security scan with a score of 9.9/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What AI apps work with Gsc?

Gsc uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Gsc MCP Server

by AKzar1el

Developer ToolsLow Risk9.9MCP RegistryRemote

Free

Server data from the Official MCP Registry

Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics.

About

Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics.

Remote endpoints: streamable-http: https://{mcp_gsc_worker_domain}/mcp

Security Report

9.9

Low Risk9.9Low Risk

Valid MCP server (2 strong, 2 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

Endpoint verified · Open access · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-akzar1el-mcp-gsc": {
      "url": "https://{mcp_gsc_worker_domain}/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

mcp-gsc

Connect in 30 seconds

Every deployed instance exposes the same endpoint shape:

https://<your-worker>.workers.dev/mcp

Claude Code

claude mcp add --transport http gsc https://<your-worker>.workers.dev/mcp

Cursor

ChatGPT — add it as a custom connector; see Connect in your AI client below.

A self-hostable Model Context Protocol (MCP) server for Google Search Console. Connect it to Claude.ai, Cursor, ChatGPT, or any MCP-compatible client and ask your AI assistant about your site's organic search performance — impressions, clicks, top queries, index status, and sitemap health — straight from your own Google account.

It runs on Cloudflare Workers and ships with one-click Google OAuth onboarding: connect the server in your client, sign in with Google once, grant the requested Google Search Console permissions, and you're done. No API keys to copy around and no service-account JSON to manage.

Prefer zero setup? The hosted version — with automatic weekly email digests delivered to your inbox — is at digestseo.com. This repository is the open-source core you can run yourself.

Tools

This server exposes 17 tools. Read-only analytics and reporting tools are marked with MCP's readOnlyHint; the write tools below can change Search Console properties, sitemaps, or indexing state.

Tool	Access	What it does
`get_capabilities`	Read	List every tool this server exposes and report whether your Google connection is currently authenticated (`connected` / `not_connected`). Takes no arguments — a good first call for discovery.
`list_sites`	Read	List the Search Console properties the connected Google account can access (`siteUrl`, `permissionLevel`).
`query_search_analytics`	Read	Impressions, clicks, CTR, and average position over a date range, with dimensions, filters, pagination, and selectable search type.
`inspect_url`	Read	Google's URL Inspection report for a single page.
`list_sitemaps` / `get_sitemap`	Read	List submitted sitemaps or retrieve one sitemap's details.
`identify_quick_wins` / `detect_cannibalization` / `detect_content_decay`	Read	Surface optimization opportunities, competing pages, and declining content.
`list_indexed_pages` / `compare_performance`	Read	Analyze pages receiving impressions and compare two periods.
`weekly_digest`	Read	Generate a plain-language seven-day performance report with movers, top pages, and one recommended action.
`add_site` / `delete_site`	Write	Add or remove a Search Console property.
`submit_sitemap` / `delete_sitemap`	Write	Submit or remove a sitemap.
`request_indexing`	Write	Request indexing for an eligible URL through the Google Indexing API.

The server requests Google Search Console and Indexing API scopes. Use a Google account with only the property access you intend to delegate, and review write-tool calls before approving them.

What you can ask

Once connected, ask your assistant things like:

"What are my top 20 queries by clicks in the last 28 days?"
"Compare impressions for example.com this month vs last month — which pages dropped?"
"Is https://example.com/pricing indexed? When was it last crawled?"
"Which queries does my blog rank position 5–15 for? Those are my quick wins."
"Give me a weekly digest for sc-domain:example.com ending today."
"Do any of my sitemaps have errors or warnings?"
"Split my clicks into brand vs non-brand using a regex on the query."
"How is my site doing in Google Discover vs regular web search?"

Connect in your AI client

Once you've deployed the server (see SETUP.md), connect it by pasting your Worker's /mcp URL into your client:

https://<your-worker>.workers.dev/mcp

Claude.ai — Settings → Connectors → Add custom connector → paste the /mcp URL. Leave Client ID and Client Secret blank. On first use, Claude opens a Google sign-in flow; grant read access and the connector turns green.
Cursor — add it as a custom MCP server pointing at the same /mcp URL.
ChatGPT (with connector/MCP support) — add a custom connector with the /mcp URL.

Any MCP-compatible client works — they all point at the same /mcp endpoint and share the same OAuth flow.

Setup

Self-hosting means bringing your own Google OAuth credentials and Cloudflare account. The full, copy-pasteable walkthrough is in SETUP.md — including an important note about Google's OAuth verification and the 7-day refresh-token limit while your app is unverified.

Quick shape:

git clone https://github.com/<you>/mcp-gsc.git
cd mcp-gsc
npm install
cp wrangler.example.jsonc wrangler.jsonc       # then paste in your KV ids
# set GOOGLE_CLIENT_ID / GOOGLE_CLIENT_SECRET / TOKEN_ENCRYPTION_KEY as secrets
npm run deploy

See SETUP.md for every step in detail.

Development

npm install
npm test              # typecheck + offline unit tests (what CI runs)
npm run dev           # wrangler dev (local)
npm run test:smoke    # structural smoke tests against a deployment

Contributions welcome — see CONTRIBUTING.md.

License

Built and maintained by Tomi Šeregi, the builder behind digestseo.com — weekly SEO digests for non-technical site owners.

Reviews

No reviews yet

Be the first to review this server!

More Developer Tools MCP Servers

Git

Free

by Modelcontextprotocol · Developer Tools

Read, search, and manipulate Git repositories programmatically

Toleno

Free

by Toleno · Developer Tools

Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.

mcp-creator-python

Free

by mcp-marketplace · Developer Tools

Create, build, and publish Python MCP servers to PyPI — conversationally.

Gsc MCP Server

About

Security Report

Findings (1)

Permissions Required

How to Connect

Documentation

mcp-gsc

Connect in 30 seconds

Tools

What you can ask

Connect in your AI client

Setup

Development

License

Reviews

No reviews yet

More Developer Tools MCP Servers

Git

Toleno

mcp-creator-python

MarkItDown

MCP Marketplace

FinAgent