Claude Code
Codex
Muse Code
Cursor
ChatGPT
Windsurf
Gemini CLI
Antigravity
VS Code
Cline
n8nGrok Build is xAI’s terminal coding agent. It can connect to remote MCP servers over HTTP, which puts live keyword, SERP, competitor, backlink, and Search Console data beside the code and pages it is already working on.
ContextBolt SEO is the hosted data layer. You add its private URL once, then ask Grok Build for the SEO job rather than opening a separate dashboard.
Add the server from the terminal
Use https://seo.contextbolt.app/mcp and complete the browser sign-in if your client supports remote MCP with OAuth. Enter your SEO account email and email code, then allow the connection. For a client that cannot complete that flow, use the personal-URL compatibility configuration shown here. Copy the full private URL from your ContextBolt SEO welcome email and replace the example URL with it.
Run this with the private URL from your ContextBolt SEO email:
grok mcp add --transport http contextbolt-seo \
https://seo.contextbolt.app/mcp/YOUR_TOKENGrok Build stores the server in ~/.grok/config.toml. If you only want it available inside one project, add --scope project to the command. The Grok Build MCP documentation covers remote transports, scopes, configuration, and the management commands.
Check the saved server and its connection:
grok mcp list
grok mcp doctor contextbolt-seoStart a Grok Build session and ask, What SEO tools do you have? The server gives it live keyword research, difficulty, SERPs, domain and competitor analysis, backlinks, AI visibility, and Search Console tools.
Grok Build, Grok Bot, and Grok are different surfaces
The names are close, but the setup is not.
- Grok Build runs in your terminal. It uses
grok mcp add, reads MCP configuration, and works beside project files. - Grok Bot is an always-on cloud agent distributed with Cursor. You add the hosted URL in chat, then use routines for scheduled work. Follow the Grok Bot integration for that path.
- Grok is the chat assistant on the web and in X. The Grok for SEO guide explains which work belongs there and which work needs a connected data source.
If the job is recurring research while your computer is closed, Grok Bot is the better shape. If the job sits beside a site or codebase you are actively changing, Grok Build keeps the research and the implementation in one terminal workflow.
What Grok Build can do with live SEO data
The useful shift is from asking for ideas to asking for evidence and an action in the same task.
For a new page, ask Grok Build to expand the topic, pull volume and difficulty, inspect the live top 10, and choose the target that fits the site’s authority. It can then use those results while it edits the page.
For an existing site, connect Search Console and ask which pages lost meaningful clicks against the previous period. Grok Build can open the relevant files, compare the page with the current SERP, and leave the proposed change in the working tree for review.
For authority work, ask for the domains that link to competitors but not to you. It can filter the result, group prospects by angle, and save a focused outreach shortlist beside the project.
These are all jobs an SEO MCP server enables: the agent decides what to do, while the server supplies the numbers and current search results it needs to decide from.
Keep the URL private
The ContextBolt SEO token sits inside the URL path, so treat the full URL like a password. Global configuration is convenient across projects. Project scope is useful when one repository needs its own server list, but keep the config out of a public repository.
The same URL also connects to Grok Bot, Cursor, Codex, Claude Code, Hermes, and OpenClaw. The SEO for agents hub maps the always-on options and routes each Grok job to its own setup.