grok-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROK_BIN | No | Path to the grok binary (default ~/.grok/bin/grok) | ~/.grok/bin/grok |
| GROK_TASK_TIMEOUT_MS | No | Per-task timeout (default 900000) | 900000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| grok_taskA | Delegate a coding task to Grok Build (headless) as a subagent. Runs in the given repository using the user's existing Grok OAuth login. Returns grok's response plus a git-verified list of files changed and commands run. For tasks likely to exceed ~1 minute, pass background: true and poll grok_task_result — long synchronous calls can hit the MCP client's request timeout. Jobs in the same cwd run serially (queued) to keep results accurate. To continue a previous task with context intact, pass its session_id. |
| grok_task_resultA | Fetch the result of a grok_task job (background, or one whose request timed out). Waits up to max_wait_ms for completion, then returns either the final result or a still-running status. Safe to call repeatedly. Results persist across server restarts. |
| grok_task_statusA | Check status of grok_task jobs without blocking. Pass job_id for one job, omit it to list all known jobs (including persisted ones from previous server sessions). |
| grok_task_cancelA | Cancel a queued or running grok_task job. Kills the grok process and returns the verified partial changes on disk. Finished jobs are not affected. |
| grok_modelsA | List available Grok model IDs (from grok's local model cache). |
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 5 tools
Each tool has a distinct purpose: listing models, starting a task, canceling, fetching results, and checking status. There is no functional overlap.
All tools follow a consistent 'grok_' prefix with snake_case, and the suffixes clearly indicate the operation (models, task, task_cancel, task_result, task_status).
5 tools cover the essential operations for the subagent-based task system: initiate, cancel, poll results, check status, and list models. No tools are missing or extraneous.
The set provides complete lifecycle coverage for tasks (create, monitor, cancel, retrieve results) plus model listing. All common agent workflows are supported without obvious gaps.