Setup / Google Search Console

This page needs JavaScript. The authorization request is prepared in your browser so that your client secret never has to be stored on a server between steps. Enable JavaScript, or run npx google-search-console-mcp auth --terminal instead.

Prerequisite

Create an OAuth client in Google Cloud

Google requires this step in their own console. Skip ahead if you already have a client ID and secret.

Open the Google Cloud Console and select or create a project.
Enable the Search Console API on that project.
Open Google Auth Platform. If the project has no consent screen yet, click Get started and fill in the four panels:
- App information. Any app name, and your own address as the user support email.
- Audience. External, unless this is a Workspace account and every user of the app is inside it.
- Contact information. Your email address, for Google's notices about the project.
- Finish. Agree to the User Data Policy, then click Create.
Go to Data access, click Add or remove scopes, and add the scope you want: .../auth/webmasters for full access, or .../auth/webmasters.readonly for read only. Click Update, then Save.
Go to Audience. Under Test users, click Add users and add the Google account that owns the Search Console properties. An External app in testing refuses every account that is not listed there.
Go to Clients, click Create client, and choose application type Web application. Name it anything.
On that client, under Authorized redirect URIs, click Add URI and paste the value labeled Authorized redirect URI on this page. Google refuses the sign-in unless it matches character for character.
Copy the client ID and client secret into the form on this page.

Authorized redirect URI

https://search-console-mcp.russjeffery.com/setup/callback

Testing mode expires tokens after 7 days. While the consent screen stays unpublished, Google invalidates refresh tokens weekly. Publishing the app, under Audience, makes them durable.

Google classes the Search Console scopes as sensitive, so a published app that has not been through verification shows an unverified app warning ahead of the consent screen. You can continue past it under Advanced. Verification matters once other people use your client; for your own account it does not.

Your client

Enter the client ID and secret

These are sent to this server once, to trade Google’s authorization code for a refresh token. Nothing is written down here: the result comes straight back to this page.