Google Search Console
Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics.
Open source Repository Open in the app JSON README (API)
About
Google Search Console MCP for analytics, indexing, sitemaps, and SEO diagnostics.
Details
- Kind
- MCP servers
- Topic
- Web search, scraping & browser
- Publisher
- akzar1el
- Origin
- official
- Category
- ferramentas
- Transport
- http
- Version
- 0.3.2-registry.1
- Stars
- 5
- Forks
- 1
- Last push
- 2026-08-31T14:16:33Z
- Repository state
- ativo
- Language
- TypeScript
- License
- MIT
- Added
- 2026-08-29 03:01:39
- Updated
- 2026-08-30 15:01:02
- Origin id
io.github.AKzar1el/mcp-gsc
README
# mcp-gsc <!-- Logo asset for marketplace submissions: assets/logo-400.png (400x400). --> [](LICENSE) [](https://modelcontextprotocol.io) [](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.AKzar1el/mcp-gsc) [](https://github.com/AKzar1el/mcp-gsc/actions/workflows/ci.yml) [](https://www.npmjs.com/package/@digestseo/mcp-gsc) [](https://glama.ai/mcp/servers/AKzar1el/mcp-gsc) Part of the **[DigestSEO](https://digestseo.com/)** suite of open-source SEO tools. - Product: [digestseo.com/gsc-mcp](https://digestseo.com/gsc-mcp/) - Engineering case study: [DigestSEO MCP Suite — AI visibility, Search Console, web validation, and trend intelligence](https://tomiseregi.si/projects/digestseo-mcp-suite) - Support: [digestseo.com/support](https://digestseo.com/support/) - Privacy: [digestseo.com/privacy](https://digestseo.com/privacy/) The self-hosting launcher is available as [`@digestseo/mcp-gsc`](https://www.npmjs.com/package/@digestseo/mcp-gsc): ```bash npx -y @digestseo/mcp-gsc ``` For Google OAuth and Cloudflare deployment configuration, follow [SETUP.md](SETUP.md). ### Connect in 30 seconds Every deployed instance exposes the same endpoint shape: ``` https://<your-worker>.workers.dev/mcp ``` The DigestSEO-hosted instance is available at: ``` https://mcp-gsc.digestseo.com/mcp ``` **Claude Code** ```bash claude mcp add --transport http gsc https://<your-worker>.workers.dev/mcp ``` **Cursor** [](https://cursor.com/en/install-mcp?name=gsc&config=eyJ1cmwiOiJodHRwczovL21jcC1nc2MuZGlnZXN0c2VvLmNvbS9tY3AifQ%3D%3D) **Kiro** [](https://kiro.dev/launch/mcp/add?name=mcp-gsc&config=%7B%22url%22%3A%22https%3A%2F%2Fmcp-gsc.digestseo.com%2Fmcp%22%2C%22disabled%22%3Afalse%2C%22autoApprove%22%3A%5B%5D%7D) Uses the hosted endpoint above; complete its Google OAuth flow on first use. **ChatGPT** — add it as a custom connector; see [Connect in your AI client](#connect-in-your-ai-client) below. A self-hostable [Model Context Protocol](https://modelcontextprotocol.io) (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](https://workers.cloudflare.com/) 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](https://digestseo.com)**. This repository is the open-source core you can run yourself. ## Tools By default (`GSC_ACCESS_MODE=readwrite`), 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. Set `GSC_ACCESS_MODE=readonly` to request only the Search Console read-only scope and expose the 12 read-only tools. | Tool | Access | What it does | |---|---|---| | **`server.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. | | **`sites.list`** | Read | List the Search Console properties the connected Google account can access (`siteUrl`, `permissionLevel`). | | **`analytics.query`** | Read | Impressions, clicks, CTR, and average position over a date range, with dimensions, filters, pagination, and selectable search type. | | **`urls.inspect`** | Read | Google's URL Inspection report for a single page. | | **`sitemaps.list`** / **`sitemaps.get`** | Read | List submitted sitemaps or retrieve one sitemap's details. | | **`insights.quick_wins`** / **`insights.cannibalization`** / **`insights.content_decay`** | Read | Surface optimization opportunities, competing pages, and declining content. | | **`indexing.list_pages`** / **`analytics.compare`** | Read | Analyze pages receiving impressions and compare two periods. | | **`reports.weekly_digest`** | Read | Generate a plain-language seven-day performance report with movers, top pages, and one recommended action. | | **`sites.add`** / **`sites.delete`** | Write | Add or remove a Search Console property. | | **`sitemaps.submit`** / **`sitemaps.delete`** | Write | Submit or remove a sitemap. | | **`indexing.request`** | Write | Requests indexing through Google's Indexing API. Google currently restricts this API to pages containing `JobPosting` structured data or livestream pages containing `BroadcastEvent` inside `VideoObject`. It is not available for general webpage submission. | Read-write mode requests the Google Search Console read-write and Indexing API scopes. Read-only mode requests only `https://www.googleapis.com/auth/webmasters.readonly` (plus `openid` and `email`) and does not register the five write tools. Read-write remains the default so existing deployments retain their current behavior; see [SETUP.md](SETUP.md) to select a mode before connecting users. > **`indexing.request` eligibility.** Google's Indexing API is not a general-purpose page submission tool — as of this writing, Google's own documentation limits it to two content types: pages with `JobPosting` structured data, and livestream pages with `BroadcastEvent` structured data nested inside `VideoObject`. Before submitting, the server fetches the target URL and checks its JSON-LD for one of those two types; if neither is present (or the page can't be fetched), it returns an error explaining why the URL is ineligible instead of calling the Indexing API. A successful submission is only an acknowledgment that Google received the notification — it does not guarantee the URL will be indexed. ## 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](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 the access requested by the deployment 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](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: ```bash 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 # choose GSC_ACCESS_MODE=readonly in wrangler.jsonc for a read-only deployment npm run deploy ``` See **[SETUP.md](SETUP.md)** for every step in detail. ## Development ```bash 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](CONTRIBUTING.md). ## License [MIT](LICENSE) © 2026 DigestSEO. --- *Built and maintained by [Tomi Šeregi](https://tomiseregi.si), the builder behind [digestseo.com](https://digestseo.com) — weekly SEO digests for non-technical site owners.*