Skip to main content

​
Overview

Connect Google Search Console by authorizing Mistle with a Google OAuth client that you create in Google Cloud. Mistle uses the OAuth authorization code flow to obtain Google access tokens. The local Google Search Console MCP server runs inside the sandbox runtime boundary and calls the Search Console API through Mistle-managed egress, where Mistle injects the connected OAuth token into outbound requests. The Google Search Console integration is read-only. Mistle requests only this OAuth scope:
  • https://www.googleapis.com/auth/webmasters.readonly

​
Prerequisites

Before connecting Google Search Console:
  1. Create or choose a Search Console property.
  2. Make sure the Google account that will authorize Mistle has access to that Search Console property.
  3. Create or choose a Google Cloud project that will own the OAuth client.
  4. If your Google Auth Platform app is in testing mode, add the authorizing Google account as a test user.

​
Enable The Search Console API

Enable the Search Console API in the Google Cloud project that owns the OAuth client: 
gcloud services enable \
  searchconsole.googleapis.com \
  --project=PROJECT_ID
Replace PROJECT_ID with the Google Cloud project ID. In Google Auth Platform, configure branding, audience, and data access for the OAuth app. Add this scope:
  • https://www.googleapis.com/auth/webmasters.readonly
For an internal Workspace rollout, select Internal audience when available. For an external app in testing mode, add every authorizing Google account as a test user before connecting.

​
Create A Google OAuth Client

Create a Web application OAuth client in Google Auth Platform.
  1. In Mistle, open Integrations and choose Google Search Console.
  2. Copy the callback URL shown by Mistle.
  3. In Google Cloud, open Google Auth Platform > Clients.
  4. Create an OAuth client with Application type set to Web application.
  5. Add the Mistle callback URL to Authorized redirect URIs.
  6. Create the client and copy its Client ID and Client secret.
  7. Return to Mistle, enter the client ID and client secret, and click Connect Google Search Console.
  8. Complete the Google consent flow with the Google account that should back the connection.

​
Connect Google Search Console To A Sandbox Profile

After the Google Search Console connection is active:
  1. Open the sandbox profile that should use Google Search Console.
  2. Add the Google Search Console integration connection to the profile.
  3. In Resources & Tools, select the Google Search Console MCP server.
  4. Publish the profile version.
Sessions using that published profile can inspect sites, search analytics data, sitemaps, and URL inspection results through the read-only Google Search Console MCP tools.

​
Access Boundary

The OAuth scope lets Mistle read Google Search Console data that the connected Google user can already access. It does not grant write access to Search Console site ownership, sitemap submission, indexing requests, or property management. For least privilege, authorize Mistle with a Google account that has access only to the Search Console properties agents should inspect.

​
Official References