feat: add Grok Build agent support

Closed
FR
2mo ago
+177-17

Motivation

I'm building a personal project and wanted to wire Neon into Grok Build. xAI ships an official plugin path, but on the Neon side there isn't clear documentation for adding the Neon MCP manually in Grok. That made add-mcp the natural place to fix the gap: one command, correct config shape, project or global.

How this PR was built

I used Grok Build (latest) against its own MCP docs to confirm user vs project paths and the native TOML schema, with Grok 4.5 high as the model. For the integration shape in this codebase, Codex was the closest existing agent (TOML + mcp_servers) and served as the reference implementation.

Summary

  • Add Grok Build as a supported agent (grok-build, alias grok)
  • Project installs write to .grok/config.toml; global installs write to ~/.grok/config.toml
  • Native TOML shape under [mcp_servers.<name>]: remote uses url + optional headers (no type field); stdio uses command / args / env
  • Document Grok Build in README, docs agents table, and landing/intro copy
  • Bump to 1.15.0 with changelog entry

Based on Grok Build’s MCP configuration docs (user scope ~/.grok/config.toml, project scope .grok/config.toml).

Test plan

  • npm run typecheck
  • npm run test (unit + e2e, including new Grok Build transform/write tests)
  • npm run build
  • Manual: npx add-mcp https://mcp.context7.com/mcp -a grok-build -y writes .grok/config.toml
  • Manual: npx add-mcp … -a grok -g -y resolves alias and writes ~/.grok/config.toml
  • Manual: npx add-mcp list-agents lists Grok Build with project + global paths

Summary by CodeRabbit

  • New Features

    • Added support for installing MCP servers in Grok Build.
    • Supports project and global configurations, including remote and local servers.
    • Added the grok alias for selecting Grok Build.
  • Documentation

    • Updated guides, website content, supported-agent listings, and changelog to include Grok Build.
    • Updated package metadata and version to 1.15.0.