SourcetoMCP
← Back to articles

How to Connect Search Console to Claude?

Published August 4, 2026 · Written by Aanart

Illustrated timber and stone cabin among pines on the shore of a still alpine lake, with snow-capped peaks and peach clouds mirrored in the water.

Contents

  1. 1Before you start
  2. 2Connect Search Console to SourcetoMCP
  3. 3Add SourcetoMCP as a connector in Claude
  4. 4Ask Claude about your search performance
  5. 5Troubleshooting
  6. 6Revoking access
  7. 7Still stuck?

This is a two-part setup: first link Search Console to SourcetoMCP like any other source, then add SourcetoMCP itself as a custom connector inside Claude. Once both are done, Claude can pull real clicks, impressions, CTR and position data straight from your verified sites instead of guessing. For what the connector covers, see the Google Search Console MCP server page.

Before you start

You'll need a SourcetoMCP account with at least one brand created, a Google account with owner or full access on at least one verified Search Console property, and a Claude account. Custom connectors work on Free, Pro, Max, Team and Enterprise, though Free accounts are limited to one at a time.

Connect Search Console to SourcetoMCP

  1. 1From your dashboard, go to Connectors → Add a connection.
  2. 2Find the Google Search Console card and select Connect.
  3. 3Sign in with the Google account that has access to the property you want. This opens Google's own consent screen on accounts.google.com and asks you to approve read-only access to your Search Console data.
  4. 4Back in SourcetoMCP, choose which verified site(s) to connect, then confirm. Each one shows up on your Connections page.

Add SourcetoMCP as a connector in Claude

  1. 1In SourcetoMCP, open Connect an agent from the dashboard sidebar and copy your server address (it looks like https://sourcetomcp.com/api/mcp).
  2. 2In Claude, open Customize, then Connectors.
  3. 3Select +, then Add custom connector.
  4. 4Paste in your server address. You can leave Advanced settings alone, because SourcetoMCP runs its own OAuth and never needs a client ID or secret from you.
  5. 5Click Add.
  6. 6The first time Claude uses it, you'll be asked to sign in to SourcetoMCP and approve access, the same OAuth approval you'd see connecting any other app. After that it reconnects on its own.

On a Team or Enterprise plan, only an Owner can add a connector, from Organization settings, then Connectors. Everyone else then opens Customize → Connectors and clicks Connect to sign in with their own SourcetoMCP account, so each person only ever reaches the sources their own account can see.

Once approved, the connection appears under Active connections on the Connect an agent page in SourcetoMCP, so you can see exactly what has access at any time.

Ask Claude about your search performance

Adding the connector makes it available, and you still switch it on per conversation. In a chat, select the + button, choose Connectors, and toggle SourcetoMCP on.

Claude shows a panel for each tool call, named in plain English, so you can see which data it pulled and check the numbers came from your account rather than from the model.

With both pieces connected, Claude can query clicks, impressions, CTR and average position for a site, broken down by date, query, page, country or device. Try something like:

  1. 1What were my top 10 search queries by clicks last month?
  2. 2Compare clicks and impressions for the last 4 weeks, broken down by page.
  3. 3Which pages have high impressions but a low click-through rate?

Search Console data typically lags a day or two behind real time, so very recent dates may come back thin. That's expected, and the connection is working normally.

Troubleshooting

My site isn't in the list when connecting: the signed-in Google account isn't a verified owner or user of that property in Search Console. Add the account under Search Console's own Settings → Users and permissions, then reconnect.

There is no Connectors option under Customize: on Team and Enterprise plans an Owner adds connectors for the whole organisation. Ask an Owner to add it from Organization settings → Connectors, and it will then show up for you to connect.

Claude won't let you add another connector: Free accounts can keep one custom connector at a time. Remove the one you have, or move to Pro or Max.

Claude says it can't find the tool or has no data: check SourcetoMCP is toggled on for that conversation under the + menu. If it is, confirm the connection still shows under Active connections in SourcetoMCP, then remove and re-add it to trigger a fresh approval.

Revoking access

You can disconnect from either side. In SourcetoMCP, remove the site from your Connections page, or revoke Claude's access entirely from the Connect an agent page. In Claude, open Customize → Connectors and remove it. On Team and Enterprise an Owner removes it for everyone from Organization settings → Connectors.

Still stuck?

Reach us at [email protected].