Google credentials

Start with Quick Connect. It needs no Google Cloud project and grants read-only access. Use your own OAuth client or a service account if you need Google write operations.

Answer setup step 1

Setup asks two questions up front. Press Enter to accept each default, or type the number of the option you want.

  1. Authentication: Quick Connect (recommended, read-only, no indexing), Custom OAuth (full access, indexing), or Service Account (full access, indexing). Quick Connect is read-only; full access needs your own OAuth client or a service account.
  2. Access level (skipped for Quick Connect): Read only (data only) or Full (data + indexing). Full access asks a separate confirmation before enabling Google write operations.

Quick Connect

Quick Connect uses the shared OAuth app and the webmasters.readonly scope. It cannot submit sitemaps or send URL indexing notifications. Setup opens Google sign-in, lets you choose properties, and saves the OAuth token on your machine under ~/.gsc-mcp/.

Connect a client with read-only Quick Connect

gsc setup --client desktop --auth shared --access readonly

Replace desktop with code, cursor, codex, opencode, or pi for another supported client. Google sign-in happens in your browser. Your MCP client and AI provider receive the tool results, subject to their own data policies. See the privacy page for details.

Read-only and full access

  • Read only (data only) is the default. It requests only webmasters.readonly and enables Search Console reads.
  • Full (data + indexing) adds the Search Console write scope webmasters and Indexing API scope indexing. It can submit sitemaps and send URL notifications. Indexing API notifications are limited to eligible pages with JobPosting or BroadcastEvent markup. Setup still asks a separate yes-or-no question before enabling writes.
  • Quick Connect is read-only. Choose custom OAuth or a service account for full access. The authenticated Google account or service account still needs permission for each property.
  • --yes accepts the defaults, so it never turns on write operations, the sample query, or the agent skill install.

Use your own OAuth client

This option uses your Google Cloud project and works with read-only or full access.

  1. Create or select a Google Cloud project and enable the Search Console API.
  2. In Google Auth Platform, set the app name, support email, audience, and requested scopes. External apps in Testing can use up to 100 listed test accounts; refresh tokens for these non-basic scopes expire after seven days. Follow Google's consent and verification steps for the scopes and audience you choose.
  3. Create an OAuth client with application type Desktop appand download its JSON file. Setup currently requires a redirect URI that starts with http://127.0.0.1. It rejects files that list only localhost or [::1]; do not edit Google's JSON to bypass that check.
  4. Keep the JSON on your machine. For example, store it at ~/.gsc-mcp/client-secrets.json and restrict access to your account:

    Create a private credentials directory

    mkdir -p ~/.gsc-mcp && chmod 0700 ~/.gsc-mcp
    chmod 0600 ~/.gsc-mcp/client-secrets.json
  5. Run setup with your client JSON and exact Search Console property ID:

    Set up Desktop OAuth

    gsc setup --client desktop --auth custom --secrets ~/.gsc-mcp/client-secrets.json --access readonly --site 'sc-domain:example.com'
    Replace the example property with your own ID. Add --site again for each additional property. Use --access full only when you need write operations.
A Desktop OAuth client secret cannot be kept secret inside an installed app. Keep your downloaded file out of source control and protect your local OAuth token. Never share or publish user tokens or service-account private keys.

Use a service account

  1. In a Google Cloud project, enable the Search Console API, create a service account, and download a JSON key. Store the key at ~/.gsc-mcp/service-account.json and restrict it to your account:

    Protect the service-account key file

    mkdir -p ~/.gsc-mcp && chmod 0700 ~/.gsc-mcp
    chmod 0600 ~/.gsc-mcp/service-account.json
  2. In Search Console, add the service account's client_emailto each property. An Owner must grant property access. Use a permission level that allows the operations you need.
  3. Run setup with the key path and property ID:

    Set up a service account

    gsc setup --client desktop --auth service-account --key-file ~/.gsc-mcp/service-account.json --access readonly --site 'sc-domain:example.com'
    Use --access full for supported write operations. Indexing API requests also require the service account to be an eligible owner and the page to use JobPosting or BroadcastEvent markup.

Google setup references

Next