Grok Bot is the cloud agent people mean when they say Grokbot. Own computer. Own logins. Routines that keep running after you close the laptop. Cursor ships it. xAI built it. Google’s first page for “grokbot seo” already mixes YouTube demos, a Cursor help doc, and a couple of agencies selling “Grok AI SEO.”
Two mix-ups to kill before the setup, because they waste a day.
Grok Bot is not the Grok CLI. The CLI, Grok Build, lives in a terminal and adds MCP servers with grok mcp add and ~/.grok/config.toml. A local server works there. Grok Bot does not run on your machine, so that local server is invisible to it.
Grok Bot is also not a Grok chat tab with plugins bolted on. Cursor’s own getting-started doc describes agents you keep around, with a cloud computer and routines. That is Hermes-shaped. That is OpenClaw-shaped. That is the thing this cluster is about.
- Grok Bot can run SEO work in the background. It cannot see keyword volume or live SERPs until you connect a data source.
- Add the MCP server in chat. There is no settings form. Tell the bot to add your public HTTPS URL.
- Localhost will not work. The bot’s computer is in the cloud, so it needs a public HTTPS endpoint. A hosted SEO MCP like ContextBolt SEO already is one.
- Use routines for research, not for publish. Search feedback takes months. Read the draft.
- ContextBolt SEO is the data layer. Keyword volume, difficulty, live SERPs and backlinks, hosted so a cloud agent can reach them. Ahrefs-grade data, not Ahrefs. Free for 7 days, then $35 a month.
What Grok Bot actually is
Each bot you create gets a persistent cloud machine. Browser, files, terminal. You sign in to the sites it needs, once, on its screen, then hand control back. Plugins cover Gmail, Notion, Slack, and a list that is still growing. Routines are the cron. Mobile is the same product, not a companion app.
That is the always-on pitch, and it is true as far as it goes. Official Cursor help is clear about the risk too. Agents can act on real accounts, files, and the web. You stay close to the first few runs.
Price is the other honest line. Access is included on every paid individual Cursor plan, Pro upward, and on Cursor Teams. You can also reach it by linking a SuperGrok, SuperGrok Plus, or SuperGrok Heavy subscription. If you pay for any of those, you already paid for the worker. The missing piece is still the SEO data. Grok Bot can browse. Browsing is not volume, difficulty, or a backlink gap.
Official Cursor help also says agents can act on real accounts, files, and the web. You sign into sites on the bot’s own screen, then hand control back. That is useful for a CMS that has no API. It is dangerous for a live title tag. The first week, sit with it. Routines come after you have watched it call the SEO tools and stop.
Sidebar sections in Grok Bot v1.2.0 let you group bots by site or client. If you run more than one property, give each one its own bot and its own Search Console connection. Mixing two domains in one transcript is how the wrong site gets the shortlist.
Why a cloud agent needs a public MCP URL
MCP is the Model Context Protocol. Anthropic released it in 2024 so agents could call tools through one standard. Cursor’s editor has had MCP for a while, via mcp.json. Grok Bot is a different runtime.
Marketplace plugins are the documented path. Custom MCP is the path people could not find, which is why the Cursor forum thread exists. A user asked how to connect a custom app on Windows. Staff replied on August 30, 2026.
There is no settings form. You tell the bot to add the server in chat.
Add this MCP server: https://your-app.example.com/mcpThe bot confirms the details and sets it up. New tools appear on the next message. The endpoint has to be reachable over the internet, public HTTPS, streamable HTTP or SSE. A server that only listens on localhost on your PC will not be reachable from the bot.
That last sentence is the whole integration. ContextBolt SEO is already https://seo.contextbolt.app/mcp/<token>. Hosted, HTTPS, streamable HTTP. It is the shape they asked for.
An SEO MCP server on the other end of that URL is live keyword research, live SERPs, difficulty, competitors, backlinks, and Search Console. Grok Bot can then use those tools while it writes, while a routine runs, and while you are in a different app.
How do you connect ContextBolt SEO to Grok Bot?
Subscribe, copy the URL, then send this.
Add this MCP server: https://seo.contextbolt.app/mcp/YOUR_TOKENWait for the confirm. Send a second message.
What SEO tools do you have? List them.You want keyword research, keyword difficulty, SERP overview, domain overview, ranked keywords, competitor keywords, plus the backlink set if you will use it. If the list is empty, the URL is wrong or the token is dead. Do not debug this by pointing at 127.0.0.1. That is the CLI, not this product.
No Authorization header. The token is in the path. Do not screenshot the chat, and do not forward the URL to a teammate in Slack. If it leaks, rotate it.
The short setup, with the four steps and the exact prompts, is the Grok Bot integration page. Hermes and OpenClaw take the same URL on their own configs. The cluster sits at SEO for agents.
If you are on the Grok CLI instead, different product, different command.
grok mcp add --transport http contextbolt-seo \
https://seo.contextbolt.app/mcp/YOUR_TOKENDo not paste that into a Grok Bot chat and expect it to work. Different runtime.
Connect Search Console after the tools show up. Ask the bot to connect it, approve read-only, and your own clicks become a free routine. That is the one feed no keyword database can fake.
Plugins versus a custom MCP URL
Cursor’s help centre documents marketplace plugins. Gmail, Notion, Slack. That is the path the UI wants you to take. Custom MCP is the path that was missing from the settings screen, which is why people were asking on the forum whether Windows could do it at all.
Staff said yes, in chat, with a public URL. That is enough for a hosted SEO server. It is not enough for a local npx process. If you were hoping to run DataForSEO’s own MCP on your laptop and point Grok Bot at it, stop. The bot cannot see your laptop. Either host that server, or use a hosted one.
Marketplace plugins and custom MCP can both be in the same bot. I would still not add two SEO data sources. The bot will pick whichever tool name sounds right, and you will spend lookups on both. One keyword server. One Search Console connection. Everything else is extra.
I pulled the live top 10 for “grokbot seo” the same day. About 108 results. YouTube, X, Reddit, Cursor’s own getting-started doc twice, one agency selling “Grok AI SEO.” The query is new. The SERP is soft. The mix-up between Grok Bot and the Grok CLI is already in the results. This post is the one that names both and tells you which config is which.
Routines that are worth running
Grok Bot’s advantage is the computer that stays on. Use it for jobs you currently forget.
Monday Search Console. A routine that pulls the last 7 days, compares to the week before, and messages you the queries that dropped with enough impressions to matter. Free, if it stays on Search Console tools.
Shortlist, then wait. You drop a topic. The bot expands it, scores difficulty, pulls the live top 10, and stops. You pick the target in chat. Then it drafts on its cloud machine, against a SERP it actually fetched. The draft can be wrong. The target cannot be a guess.
Competitor watch. Weekly, not daily. Ranked keywords the rival gained. A backlink gap if you have the credits. Three lookups per backlink call, so do not loop it.
Teach-a-task is tempting here. Grok Bot can watch you click through a workflow and repeat it. Fine for a Beehiiv stats pull. Not fine as a substitute for keyword data. A recording of you opening Ahrefs is still you opening Ahrefs. An MCP call is the agent having the numbers when you are not there.
Where ContextBolt SEO fits
I built ContextBolt SEO so the agent you already work in can pull Ahrefs-grade data without a dashboard to learn. $35 a month, 1,000 lookups, 7-day trial. Grok Bot is one of the first runtimes where “already work in” means the work continues after the laptop lid shuts.
That makes the credit discipline stricter, not looser. A routine that fires every hour will spend the month by Thursday. Check the balance. That call is free. Use Search Console for your own site. Spend paid lookups on terms you do not already rank for.
Findings land in the chat and on your SEO Board. Grok Bot is not a git checkout, so ./seo-findings/ is not the metaphor. The board is. Open it when you want the receipts without scrolling a transcript.
Ahrefs-grade, not identical to Ahrefs. Directionally accurate. Good enough to pick a target. Not good enough to fight a client about a decimal.
The honest limits
Grok Bot can use a browser on its own computer. That is the feature people demo. It is also how you get an agent that “researches” by skimming titles and then writes a post that cannot rank. If the MCP tools are connected, tell it to use them before it drafts. If they are not connected, do not ask it for a content calendar.
Routines do not get you off the hook. A scheduled publish is still a publish. The SEO automation post is blunt about this. Lookups and comparisons are safe to automate. Live URL writes are not.
Price of the bot itself is not our price. ContextBolt SEO is $35. Grok Bot started out gated to the top tiers, so older write-ups will tell you it is out of reach. Cursor’s current help says access is included on every paid individual Cursor plan, Pro upward, and on Cursor Teams, or by linking a SuperGrok subscription. If you already pay for the bot, the data layer is the cheap part.
No model picker, at least at launch. The bot chooses. Fine for keyword lookups. Less fine if you wanted a specific model to draft in your voice. Keep the draft in chat, rewrite it yourself, or move the writing step to Claude Code once the shortlist is done.
And we do not put Grok on the rest of the site as a default client. This page is Grok Bot, the cloud agent, with a verified custom-MCP path. The homepage roster stays the clients we have claimed all along.
One more practical split. Cursor the editor still has mcp.json. Grok Bot does not read that file. Adding ContextBolt SEO to Cursor does not add it to Grok Bot, and the reverse is also true. If you use both, you connect twice. Same URL, two runtimes.
When the bot offers to “just look it up” in the browser instead of calling a tool, say no. Browser titles are not volume. A rendered SERP in a cloud Chrome is not serp_overview. The whole point of the MCP URL is that the number comes back as data the next step can use, not as a screenshot the model then hallucinates a KD onto.
Give the bot a public URL, a routine, and a rule that publish waits for you. That is the version of SEO with Grok Bot that will still look smart in three months.