Google Search Console MCP Server

An MCP server that gives Claude and other AI agents real control over Google Search Console — list your properties, check whether a URL is indexed, submit sitemaps, pull search analytics, and diagnose setup problems, all from a conversation.

Built for SEO practitioners tired of checking index status and submitting sitemaps by hand, one property at a time, and for the AI agents that can do it for them.

---

Project status

Pre-alpha. The whole surface is wired up, including submission; none of it has met a real Google account yet.

Fifteen tools are registered on the server and covered by a wire-level smoke test that connects a real MCP client session and confirms every tool answers with a description. Storage, quota accounting, OAuth, and config are the foundation underneath them. Sign-in has been walked for real, once, on Windows against a live Google account — see docs/manual-smoke.md, which is also where the two defects that run found are recorded. Submission exists end to end in code and no URL has been submitted through it; see Known gaps.

Milestone	Scope	State
1. Foundation	Paths, logging, SQLite store, quota engine, OAuth + PKCE, config	Done
2. MCP surface	The tools below, exposed over MCP	Done
3A. Onboarding	Guided sign-in, browser/profile detection, the bridge extension	Done
3B. Submission	Browser-driven Request Indexing, job control	Code complete, unverified
4. Reporting	Indexation discovery and audits	Code complete, unverified

Watch or star the repo if you want to know when the milestones above are verified against live properties.

Tools

Shipped and registered on the MCP server today:

Tool	What it does
gsc_list_sites	List every Search Console property the account can reach
gsc_doctor	Diagnose auth, config and environment problems
gsc_check_status	Index status for one or more URLs via the URL Inspection API (read-only, spends no Request-Indexing slot)
gsc_quota	Request-Indexing and URL Inspection budget remaining today, per property
gsc_performance	Clicks, impressions, CTR and position from Search Analytics
gsc_submit_sitemaps	Submit or resubmit sitemaps to a property
gsc_setup	Walk through sign-in and setup; idempotent, returns the single next step
gsc_detect_browsers	Locate installed browsers and profiles for browser-driven submission
gsc_use_browser	Pin the browser profile to drive, overriding the detector's recommendation
gsc_request_indexing	Submit up to five URLs for indexing, one at a time. Blocks for minutes — see Submitting URLs
gsc_start_indexing_job	Queue a background submission run over any number of URLs; returns at once
gsc_job_status	Progress and state for one submission job, or the most recent
gsc_stop_job	Ask a running submission job to stop after the URL in flight
gsc_find_unindexed	Find which of a property's URLs are not indexed, and why — see Finding what is not indexed
gsc_audit	The current indexation position for a property, read from the local store; spends no quota

Why quota accounting is the hard part