grok-build-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROK_HOME | No | Home directory for Grok (passed through to the child process) | |
| GROK_BINARY | No | Path to the grok executable | grok |
| XAI_API_KEY | No | API key for the Grok CLI (passed through to the child process) | |
| GROK_MCP_LOG_LEVEL | No | `debug`, `info`, `warn`, `error`. Logs go to stderr | info |
| GROK_MCP_STATE_DIR | No | Background job records | $XDG_STATE_HOME/grok-mcp |
| GROK_MCP_TIMEOUT_MS | No | Wall clock for a single run | 1800000 |
| GROK_MCP_DEFAULT_MODEL | No | Model when a call omits one. `none` defers to the CLI | grok-4.6 |
| GROK_MCP_DEFAULT_EFFORT | No | Reasoning effort when a call omits one. `none` defers to the CLI | high |
| GROK_DISABLE_AUTOUPDATER | No | Disable auto-updater (passed through to the child process) | |
| STRUCTURED_CONTENT_ENABLED | No | Also emit `structuredContent` alongside `_meta` | off |
| GROK_MCP_DEFAULT_PERMISSION | No | Level used when a call requests none | read-only |
| GROK_MCP_PERMISSION_CEILING | No | Highest level any call may request | read-only |
| GROK_MCP_MAX_CONCURRENT_RUNS | No | Background runs alive at once. `off` for no cap | 4 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| checkA | Report grok-build-mcp-server status: version, resolved grok binary, permission ceiling, CLI readiness ( |
| grokA | Run a headless Grok Build agent ( |
| reviewA | Review a git diff with Grok Build. Targets the working tree ( |
| sessionsA | List and search Grok Build sessions from the local store ($GROK_HOME/sessions). Search is local-only: it does not consult |
| websearchA | Research a question with Grok Build's web search. |
| statusA | Poll a background |
| stopA | Terminate a background |
| helpA | Show the grok CLI help text. Runs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool maps to a clearly distinct operation: general agent run, specialized read-only review, web research, background run status, background run termination, session lookup, environment check, and CLI help. The only potential overlap is between grok, review, and websearch, but their descriptions sharply differentiate the general execution mode from the two read-only specialized modes.
All tool names are short, lowercase, single words, so there are no case or separator inconsistencies. However, the set mixes action verbs (check, help, review, stop), resource-like nouns (status, sessions), and a product name (grok), so it follows a loose CLI-subcommand style rather than a strict verb_noun naming convention.
Eight tools is well-scoped for a CLI wrapper server: core execution, two specialized read-only operations, background run lifecycle management, session inspection, diagnostics, and help. Each tool earns its place and none feels redundant.
The toolset covers the full workflow of running Grok Build headlessly, including general runs, diff reviews, web searches, background polling, cancellation, session discovery, and environment readiness checks. While session deletion/export is not exposed, session resumption is supported via the grok tool and sessions tool, so there are no dead ends.