mcp-grok-executor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROK_BIN | No | Path to the Grok CLI | grok |
| GROK_AUTH_PATH | No | Auth file checked by auth_status | ~/.grok/auth.json |
| MCP_GROK_MODEL | No | Default -m passed to Grok (CLI default) | |
| MCP_GROK_CACHE_DIR | No | Job records + logs | ~/.cache/mcp-grok-executor |
| MCP_GROK_TRANSPORT | No | cli (default) or acp (experimental) | cli |
| MCP_GROK_TIMEOUT_SEC | No | Default timeout per Grok run | 600 |
| MCP_GROK_REVIEW_TOOLS | No | Tool allowlist for review_task (read-only set) | |
| MCP_GROK_MAX_OUTPUT_CHARS | No | Truncation budget for inline output | 80000 |
| MCP_GROK_REVIEW_DISALLOWED | No | Tools stripped in review_task (write/shell set) |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Check whether Grok CLI is logged in via ~/.grok/auth.json (subscription OAuth). Call this before first use if unsure. |
| review_taskA | READ-ONLY: Ask Grok to analyze code, review a plan/diff, or answer questions without mutating files. Prefer this before execute_task. Grok runs without --always-approve and with write/shell tools disabled. |
| execute_taskA | MUTATING: Delegate implementation to Grok (file edits, tests, shell). Uses --always-approve. Only call after the user approved a plan or explicitly asked to implement. Verify with git diff/tests afterwards. Returns session_id for continue_task. |
| continue_taskA | Continue a previous Grok execution session with a follow-up prompt (e.g. fix failing tests). Prefer session_id from a prior execute_task; otherwise continues the most recent session in cwd. |
| run_taskA | ORCHESTRATED + MUTATING: run a full execute → git-evidence → verify → auto-fix loop server-side and return structured evidence (attempts, changed files, diff, verify output). Same approval bar as execute_task: only after the user approved a plan. Prefer this over execute_task when a test/build command can verify the work. If the result has status 'needs_advisor', answer the question via continue_task with the returned session_id. cancel_task also aborts in-flight grok sub-processes. |
| task_statusA | Poll a background job started with background=true, or list recent jobs if job_id is omitted. |
| cancel_taskA | Cancel a running background Grok job by job_id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| recent-jobs | Last 20 grok job records (newest first) |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/emigrete/mcp-grok-executor'
If you have feedback or need assistance with the MCP directory API, please join our Discord server