Skip to main content
Grok Build is xAI’s coding agent for the terminal: the grok CLI. This is the terminal agent, not Grok Build on grok.com or in the apps. It also runs headless in scripts and inside other apps, and its source is open under Apache 2.0. Add PostQueen with one command and Grok Build can announce a release, draft posts from your repo and report how published posts did, without leaving the terminal.
A sample Grok Build terminal session with PostQueen connected: a request for posts, the PostQueen tools it used, and the reply

Before you start

  • Plans: xAI’s pricing lists Grok Build on every plan, with limited use on Free. Sign in through the browser, with grok login --device-auth, or with an xAI API key.
  • Platforms: the terminal on macOS, Linux and Windows. WSL uses the Linux build.
  • A PostQueen API key. A workspace admin copies it, or the ready-made address, from Connections.
Where the API key is: in the app, open Connections > API key. Only a workspace Admin or Super Admin can reveal or rotate it; other members see it masked. A workspace has one key, and each agent card on Connections shows your MCP address with the key already filled in.

Connect Grok Build

1

Add PostQueen

Run this in your terminal, with your key in place of YOUR_API_KEY:
It saves PostQueen in your user config, ~/.grok/config.toml, so every project can use it.
2

Check the server

Run the doctor, or type /mcps inside Grok Build to open the extensions modal:

Check that it works

Start Grok Build and ask: “List my PostQueen channels.” It calls PostQueen and answers with the channels you connected. If PostQueen is missing, run grok mcp list to see whether the server is saved.

Good to know

  • Keep the key out of the file with the header form under Other ways to connect. The command above writes the key into config.toml.
  • One project only: add --scope project to write .grok/config.toml in the project instead of your user config.
  • Grok Build also reads ~/.claude.json, .cursor/mcp.json and a project .mcp.json, at a lower priority than its own config. A server you already added for Claude Code or Cursor can show up here too.
  • Ask for drafts when you want to check first. A draft waits on your PostQueen calendar, and nothing publishes until you schedule it.
  • What it cannot do over MCP: change a post’s text or time. Do that on the calendar in the app. The MCP tools lists what it can do.

Other ways to connect

Grok reads ${POSTQUEEN_API_KEY} from your environment when it loads, so the key stays out of config.toml:
Keep the single quotes. With double quotes your shell writes the key itself into config.toml.

Try this first

The draft appears on your PostQueen calendar, ready for you to check and schedule. Prompts to try has more.

Troubleshooting

More fixes are on Troubleshooting agents.

Is it the same as Grok or Grok Bot?

No. xAI has three products with Grok in the name, and each one connects to PostQueen on its own: A server in Grok Build’s config.toml does not reach Grok on grok.com or Grok Bot.

Next steps

Every agent

Which agents can post to PostQueen, and how each one connects.

The MCP tools

What each of the 25 tools does, and what an agent cannot do.

Prompts and tool calls

The order an agent calls the tools in, with prompts that work.

Troubleshooting agents

What to do when a connection or a command fails.
Last modified on October 27, 2026