How to Connect Google Search Console to Grok Bot (xAI Cloud Agents + MCP)

Grok Bot is xAI's take on the always-on agent: named AI teammates that live on a cloud computer with a browser, files and a terminal, keep memory between sessions, and run routines on a schedule after you close your laptop. Connect one to the hosted Search Console MCP and SEO maintenance becomes something your Bot does every Monday morning with your real queries, clicks and positions, not something you remember to check. Setup is one URL plus a token; here is the whole thing.

What Grok Bot is (and why it fits Search Console)

Launched in beta on August 11, 2026, Grok Bot sits on xAI's top plans (SuperGrok Heavy, Cursor Ultra and eligible team plans). You create named Bots, give them standing instructions, and they work persistently: routines run on schedules, successful processes become reusable skills, up to six Bots can pass work between themselves in group chats, and sensitive actions wait for your approval.

That shape rewards exactly what SEO needs: boring consistency. Rankings drift, pages fall out of the index quietly, Core Web Vitals regress after an unrelated deploy. None of it announces itself; it has to be noticed. An agent that reads your Search Console data every week and only pings you when something moved is the right tool, and because the Search Console MCP is read-only by construction, an autonomous Bot can observe your site but never change anything.

The two Grok Bot constraints that decide the setup

• Remote MCP servers only. Grok Bot attaches MCP servers over HTTPS on the public internet. It cannot run local stdio servers and cannot reach localhost, so the classic "clone an open-source GSC server and run it on your machine" route is out (or means running a tunnel forever). A hosted server is the supported path, not just the convenient one.
• No interactive OAuth yet. In the current beta, custom connectors take a server URL plus a static auth header; Grok Bot cannot drive a sign-in flow the way Claude or ChatGPT do. That is what our manual setup token is for: you do the Google sign-in once in your own browser, then hand the Bot a bearer token.

Connect it, step by step

1. Get your setup token. Sign in with Google here (approve the read-only Search Console scope), then on your account page click Generate setup token. Copy it now; we store only a hash, so it is shown exactly once.
2. Add the plugin in Grok Bot. Open Settings → Plugins, add a custom connector, and set the server URL to https://mcpsearchconsole.com/mcp.
3. Set the auth header. In the connector's auth field, use Authorization: Bearer <your token>.
4. Attach and verify. Connectors become available to attach to a task with @, alongside your Bots and routines. Attach Search Console and ask: "List my Search Console properties." If your sites come back, your Bots are connected.

From then on any Bot on the account can call the server's tools: search performance with filters and period comparisons, URL inspection, sitemaps, PageSpeed and site-health checks for DNS, redirects, robots.txt and TLS.

Three routines that maintain your SEO

Give a Bot these as scheduled routines and you cover most of the weekly grind. They are deliberately small; a Bot that messages five bullet points every Monday beats a dashboard nobody opens.

Grok Bot's memory is what makes the second routine work: "compare with last run" is only computable because the Bot persists files between runs. If you want the full self-improving loop, with hypotheses and verified predictions, the design in our autonomous SEO agent guide transfers unchanged.

Using grok.com chat instead?

Regular Grok on grok.com also takes custom MCP connectors, and there the OAuth flow works: go to grok.com/connectors, click New Connector, choose Custom, paste https://mcpsearchconsole.com/mcp and sign in with Google when prompted. No token needed; that route is interactive chat rather than scheduled teammates.

Using a different assistant? The picker below has the same setup for Claude, ChatGPT, Cursor, Codex and more.

Troubleshooting

• The connector won't accept an OAuth sign-in. Expected in the current beta: Grok Bot has no interactive OAuth for custom MCP servers. Use the setup-token route above; the token stands in for the sign-in you completed in your own browser.
• You lost the token. Generate a new one from your account page. Generating a new token replaces the old one, so update the plugin's auth header after regenerating.
• Grok Bot rejects the URL. It only accepts servers reachable on the public internet. https://mcpsearchconsole.com/mcp is public, so a rejection usually means a typo (the path is /mcp, not /).
• Several Bots, one quota. Connectors are shared account-wide, not per Bot, and every Bot's data pulls draw on the same tenant quota. Free-plan caps that fit one weekly digest can bind when three Bots each run their own routine; space the schedules or upgrade.
• Empty results for your site. Have the Bot list your properties first. sc-domain:example.com and https://example.com/ are different Search Console properties; put the exact one in the routine's standing instructions.
• "Yesterday" looks empty. Search Console data trails by about two days. Write routines against trailing windows (last 7 or 28 days), never "yesterday".

Quota and pricing

Connecting is free: discovery and site-health tools are unlimited, and data pulls (performance queries, URL inspection, sitemaps, PageSpeed) are metered per day and month on the free plan. A weekly digest plus a monthly sweep fits the free plan comfortably; an account full of Bots running daily routines is exactly the case Solo's unlimited pulls are for, at a few euros a month next to Grok Bot's own price tag.

Go further

The always-on pattern is bigger than one product: our OpenClaw and Hermes guide runs the same three routines on self-hosted agents, and the autonomous SEO agent guide adds the full hypothesis-and-verify loop. For interactive analysis in chat, the Claude guide and ChatGPT guide are the one-minute versions. And for what to stack next to Search Console (backlinks, crawling, conversions), see the best SEO MCP servers comparison.