SourcetoMCP
← Back to articles

How to Connect Search Console to Grok?

Published September 22, 2026 · Written by Aanart

Illustrated stone dam spilling waterfalls under dramatic storm light breaking over distant peaks.

Contents

  1. 1Before you start
  2. 2Connect Search Console to SourcetoMCP
  3. 3Add SourcetoMCP as a custom connector in Grok
  4. 4Ask Grok 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 Grok. Once both are done, Grok 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 Grok account. Custom connectors on grok.com need a SuperGrok plan, either standalone or through X Premium+. On a Grok Business or Enterprise seat, a team admin provisions the connector instead, see the note in the next section.

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 custom connector in Grok

  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. 2Go to grok.com/connectors and select New Connector.
  3. 3Choose Custom.
  4. 4Paste in your server address and complete the authentication step so Grok can reach it. SourcetoMCP runs its own OAuth, so there is no client ID or secret to enter.
  5. 5Approve access when Grok asks for it, the same as you would for any other connector.

On a Business or Enterprise plan, a team admin adds the connector first, from console.x.ai's Grok Business → Connectors, choosing Add Connector, then Other, and pasting the same server address. Once it's provisioned, each team member opens grok.com/connectors themselves and signs in with their own SourcetoMCP account, so a 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 Grok about your search performance

Once it's added, SourcetoMCP is available to Grok in any conversation, there is no separate toggle to switch on per chat. Grok discovers the tools the server exposes and calls them the same way it uses any of its built-in connectors.

The connector covers four things: search performance (clicks, impressions, CTR and average position by date, query, page, country or device), submitted sitemap status, real-time index status for a single URL, and the list of properties your account can access. Try something like:

  1. 1Give me a country breakdown of clicks and average position for the last 90 days.
  2. 2Which of my submitted sitemaps have indexing errors right now?
  3. 3Is /pricing indexed, and what does Google think its canonical URL is?

Search Console's own numbers usually run a day or two behind, so a report for today or yesterday can look thin. That's the source data, not a sign anything is broken.

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.

New Connector → Custom isn't available on grok.com: custom connectors need a SuperGrok plan on an individual account. On a Business or Enterprise seat, a team admin has to provision the connector first from console.x.ai before it shows up for anyone else.

Grok says it can't find the tool or has no data: check the connector still shows as connected under grok.com/connectors. If it does, 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 Grok's access entirely from the Connect an agent page. In Grok, open grok.com/connectors and remove it. On Business and Enterprise, a team admin removes it for everyone from console.x.ai.

Still stuck?

Reach us at [email protected].