Skip to main content
Grok Build is xAI’s terminal coding agent. It is not Grok chat at grok.com, and it is not Grok Bot. Same pairing as Claude Code vs Claude. Official install is one command. It writes ~/.grok/config.toml. A custom connector at grok.com/connectors does not register this product.
You need your PostQueen API key first. In app.postqueen.ai, open Settings → API Keys and click Reveal.

​
Add via CLI

Replace YOUR_API_KEY with your actual key. grok mcp list shows the postqueen server. grok mcp doctor postqueen diagnoses connectivity.

​
The two forms

The same registration grok mcp add writes, done by hand:
~/.grok/config.toml
Syntax per the official xAI MCP servers page. Pass --scope project to write .grok/config.toml in the current repo. Grok Build also loads ~/.claude.json and Cursor mcp.json at lower priority. Disable that with [compat.cursor] mcps = false if you only want the grok command.
Your API key grants full access to your PostQueen workspace: treat it like a password. ~/.grok/config.toml is plain text. If the key leaks, regenerate it in Settings → API Keys and update every client that uses it.

​
Self-hosted

On a self-hosted instance, replace https://api.postqueen.ai with your NEXT_PUBLIC_BACKEND_URL, for example https://postqueen.example.com/api/mcp/YOUR_API_KEY. Most self-hosted setups serve the backend under /api.
Your reverse proxy has to forward the /mcp paths and stream the response rather than buffering it. The configuration, and the Nginx setting that silently breaks this, are on MCP on a self-hosted install.

​
Verify

Run grok mcp list, then ask Grok Build:
“List my connected social media accounts”
Your channel names come back, because the agent reached for her integrationList tool.

​
Next steps

Grok Build as an agent

Skill plus CLI in the same terminal session

Grok chat

Custom connector at grok.com/connectors, not this product

Grok Bot

Cloud agent. Add the server in the Bot chat.

MCP tools

All 14 tools, with every parameter