Skip to main content

Set up the Google Search Console MCP server

The Google Search Console MCP server provides search analytics, URL inspection, URL indexing, and sitemap management for any property you have access to in Search Console. This guide covers enabling the required Google APIs, creating an OAuth client in Google Cloud, and connecting the server to MintMCP.

Prerequisites​

  • A MintMCP admin account
  • A Google Cloud project with an OAuth consent screen already configured, plus permission to enable APIs and create OAuth credentials
  • Access to at least one property in Google Search Console

Enable the APIs​

  1. Go to console.cloud.google.com and select or create a project.
  2. Go to APIs & Services → Library and enable both:

Create the OAuth client​

The OAuth client gives MintMCP a client ID and secret to broker each user's Google sign-in. The Google Cloud OAuth flow is the same as the Google Ads MCP setup — the screens are identical.

  1. Go to console.cloud.google.com/auth/clients and click Create client.

  2. Set Application type to Web application and give it a name (for example, MintMCP OAuth).

    Create OAuth client ID form with application type set to Web application and a name field

  3. Under Authorized redirect URIs, click Add URI and enter MintMCP's callback URL:

    https://app.mintmcp.com/oauth/callback

    Leave Authorized JavaScript origins empty. This URI must match the Redirect URL in the connector's OAuth settings exactly, or sign-in fails with redirect_uri_mismatch.

    Authorized redirect URIs field set to the MintMCP OAuth callback URL

  4. Click Create. Google shows the Client ID and Client secret once — copy both now, because you can't view the secret again after closing the dialog.

    OAuth client created dialog showing the Client ID and Client secret

Reopen the client anytime from the Clients list to edit its redirect URIs or rotate the secret.

OAuth client detail page showing Client ID, redirect URIs, and the client secret with rotation options

App verification​

If you publish the OAuth app to users outside your Workspace organization, Google's verification review requires declaring the scopes it requests on the OAuth consent screen:

ScopePurpose
https://www.googleapis.com/auth/webmastersSearch Console read and write — analytics, sitemaps, URL inspection
https://www.googleapis.com/auth/indexingIndexing API — submit and remove URLs

Internal apps used only within your Workspace organization don't need verification.

Add Google Search Console to MintMCP​

  1. In MintMCP, go to MCP store → Manage store.

  2. Find the Google Search Console connector and click to install it.

  3. Open the connector's OAuth settings and enter:

    SettingValue
    Authorization URLhttps://accounts.google.com/o/oauth2/v2/auth?access_type=offline&prompt=consent
    Token URLhttps://oauth2.googleapis.com/token
    Scopehttps://www.googleapis.com/auth/webmasters https://www.googleapis.com/auth/indexing
    Client IDClient ID from the OAuth client you created
    Client SecretClient Secret from the OAuth client you created

    access_type=offline is required so Google issues a refresh token. MintMCP stores it and injects a fresh access token into every request — the server never refreshes tokens itself.

  4. Confirm the Redirect URL shown in the connector's OAuth settings matches the URI you added to the OAuth client (https://app.mintmcp.com/oauth/callback). They must be identical.

  5. Click Save.

The first time a user calls a tool, MintMCP directs them to sign in with Google and consent to the two scopes. MintMCP stores and refreshes their token automatically on every subsequent call.

Security considerations​

  • Each user authenticates individually through OAuth, so tool calls run against that user's own Search Console access — bounded by their existing property permissions.
  • The server can read and write: alongside analytics and URL inspection, it can submit and remove URLs via the Indexing API and add and delete sitemaps. Those writes are limited to properties the signed-in user can already manage.
  • The webmasters and indexing scopes grant broad API access; what the server can actually do is bounded by its tool surface, not narrowed by the scopes.

Next steps​