gsc_doctor
Diagnose whether your Google Search Console MCP is correctly configured by running seven checks on OAuth, token, config, store, properties, browser, and extension, with fixes for each failure.
Instructions
Diagnose whether gsc-mcp is set up to talk to Search Console.
Runs seven checks in order — oauth_client, token, config, store,
properties, browser, extension — and reports all of them even if one
raises. A check that raises is recorded as ok: False with the
exception's TYPE NAME only in detail; the message is never included,
because it can carry a bearer token, a credentialed URL, a raw response
body, or a filesystem path holding your account name. Every failing
check carries a non-empty fix string with a concrete next step; this
tool diagnoses, it does not repair anything itself.
The last two are the local setup for browser-driven submission, and
they come last because they cost nothing and the first five establish
whether anything works at all. browser names the profile to use;
extension reports whether the bridge extension is REGISTERED in that
profile — a green check does not mean its background worker is
running, which needs a live connection and arrives with Milestone 3B.
"Could not be checked" is reported as such, never as "not installed".
Costs at most one Search Console API call (sites.list, for the
properties check); the browser and extension checks are local file
reads and make none.
Returns {"ok": bool, "checks": [{"name", "ok", "detail", "fix"}, ...]};
ok is true only when every check passed.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||