Codex Delegate vs Grok Build

A side-by-side look at the Codex Delegate and Grok Build MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Codex Delegate logoCodex DelegateCoding Agents · Local subprocess (stdio)Bridge AI coding hosts to the OpenAI Codex CLI for delegated implementation.63GoodAuth: not declaredGrok Build logoGrok BuildCoding Agents · Local subprocess (stdio)Run the Grok Build CLI as MCP tools: agent runs with live progress, code review, web research.53GoodAuth: not declared

Verdict: choose Codex Delegate for coding agents work as a local process; choose Grok Build for coding agents as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Codex Delegate logoChoose Codex Delegate when

  • You need dedicated capabilities in the Coding Agents domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like delegate, cancel, doctor.
Explore Codex Delegate

Grok Build logoChoose Grok Build when

  • You need dedicated capabilities in the Coding Agents domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like grok, review, websearch.
Explore Grok Build

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCodex Delegate logoCodex DelegateGrok Build logoGrok Build
CategoryCoding AgentsCoding Agents
Quality signal63/100 · Good53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingBYOK (pay the provider)Not declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars20
Directory activity 6 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools38

Tools & capabilities

Codex Delegate tools 3

  • delegateDelegate a coding task to OpenAI Codex. Never run codex from the shell — use this tool. Check status before trusting result — a run that spawns then fails returns normally. Keep model, reasoningEffort and fast at their defaults unless the user asks. See the delegate skill.
  • cancelCancel active runs. delegationId selects one (announced in progress before spawn — the only handle if a run wedges at startup), threadId all on its thread, neither all. Waits for settlement; if a process tree survives the kill deadline, it still returns and the delegate result warns. Status: cancelled, nothing-active, or not-found (no active run with this ID).
  • doctorDiagnose plugin/CLI/login, recursion, and workspace (default: server cwd). deep adds no-quota help and model-catalog checks.

Grok Build tools 8

  • grokRun a headless Grok agent. Prompt, session resume/continue/fork, model, effort, tool allow/deny
  • reviewReview a git diff: working tree, a merge-base diff against a ref, or a single commit
  • websearchResearch a question on the web, and report which searches and sources it actually used
  • statusPoll a background run, or list recent ones
  • stopTerminate a background run's process tree
  • sessionsList, search, and look up the Grok sessions on this machine
  • checkServer version, resolved binary, `grok version`, auth, permission ceiling, run defaults
  • helpgrok --help` passthrough

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Codex Delegate

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "codex-delegate": {
      "command": "npx",
      "args": [
        "-y",
        "codex-delegate-mcp"
      ]
    }
  }
}

Grok Build

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "grok-build": {
      "command": "npx",
      "args": [
        "-y",
        "grok-build-mcp-server"
      ]
    }
  }
}

Frequently asked questions

Codex Delegate is categorized under Coding Agents and uses a local stdio subprocess. Grok Build belongs to Coding Agents and uses a local stdio subprocess. Pick Codex Delegate for coding agents work and Grok Build for coding agents.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Codex Delegate is bring-your-own-key: usage is billed by the API provider you supply a key for. Grok Build has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add codex-delegate and grok-build as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Codex Delegate has a quality signal of 63/100 (Good) with 6 views, 0 installs and 2 GitHub stars. Grok Build has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.