bloggerclinic/connectors

Docs · Search Console MCP

Create your Google OAuth client.

Ten minutes, once, no billing account. At the end you have a client id and secret that belong to you — the consent screen you approve is yours, and revoking it from your Google account cuts us off instantly. Screens are named exactly as Google labels them (verified 2026-08; Google occasionally renames — the changelog notes re-verifications).

  1. 01Open the Google Cloud console

    Go to console.cloud.google.com signed in as the Google account that owns (or can view) your Search Console property. If you have never used Cloud before you will be asked to accept the terms — no billing account is needed for any of this.

  2. 02Create a project

    Top bar → the project picker (left of the search box) → New project. Name it anything (“search-console-mcp” works), leave Location as “No organisation”, press Create, then make sure the picker now shows that project.

  3. 03Enable the two APIs

    Left menu → APIs & Services → Library. Search “Google Search Console API” → Enable. That single API covers search analytics, sitemaps, and URL inspection.

  4. 04Configure the consent screen

    APIs & Services → OAuth consent screen. Google now calls this “Google Auth Platform” — if you land on a get-started wizard: App name = anything, User support email = your email, Audience = External, add your email as the developer contact, agree, Create. You do not need to submit the app for verification: under Audience → Test users → Add users, add your own Google account email. Test mode with yourself as the only test user is the intended end state — this client is for you alone.

  5. 05Create the OAuth client

    APIs & Services → Credentials → + Create credentials → OAuth client ID. Application type = Web application. Name = anything. Under Authorised redirect URIs → + Add URI, paste exactly:

Authorised redirect URI — paste exactly
https://gsc-mcp.bloggerclinic.com/oauth/callback

(Self-hosting? Use your own worker's origin instead.) Press Create. A dialog shows Client ID (ends in .apps.googleusercontent.com) and Client secret (starts with GOCSPX-). Copy both.

06Hand them to the connector

In any Claude conversation with the connector installed:

in Claude
Use gsc_setup with
client_id: 1234…apps.googleusercontent.com
client_secret: GOCSPX-…

The tool returns an authorize_url. Open it, pick the same Google account, click through the “Google hasn't verified this app” notice (it is your unverified app — Continue is the correct answer), approve the Search Console scope, and you land on a “Search Console connected” page. Back in Claude: gsc_auth_status → connected: true, then gsc_list_sites.

If it goes wrong

  • redirect_uri_mismatch: the URI in step 05 differs from what you pasted — fix it in Credentials → your client → redirect URIs. Exact match, no trailing slash.
  • access_denied / app not verified: your email is missing from Test users (step 04).
  • invalid_client: the secret was rotated or copied with whitespace — run gsc_setup again.
  • Google expires refresh tokens of test-mode apps after 6 months of disuse; if status flips to disconnected, reopen the authorize URL — 30 seconds.