grok-delegate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROK_DELEGATE_JOBS_DIR | No | Optional directory for durable job artifacts. | |
| GROK_DELEGATE_LANES_PARENT | Yes | Parent directory for isolated git worktrees, outside the repo. | |
| GROK_DELEGATE_ALLOWED_ROOTS | Yes | Allowlisted project roots (fail-closed); empty allowlist rejects work. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| grok_agent_statusB | Version/auth-presence, exact roots, transport router, daemon and durable job status. Read-only. |
| grok_agent_startC | Asynchronously start a versioned typed task packet on an explicit legacy|stdio|websocket transport. auto means stdio only. |
| grok_agent_pollC | Read bounded progress/events and the final evidence receipt for a typed job. |
| grok_agent_cancelB | Boundedly cancel one typed job without stopping the MCP server. |
| grok_agent_consultB | Start an isolated read-only consult session; non-git exact allowlisted roots are supported. |
| grok_agent_reviewB | Start an independent read-only skeptic session over supplied evidence/diff inputs. |
| grok_agent_executeC | Start workspace execution in a git worktree. completed requires a real diff and requested evidence. |
| grok_agent_fixC | Start a separate workspace fixer session scoped to confirmed findings in the task packet. |
| grok_delegateA | Delegate a coding goal to local headless grok in an isolated git worktree on a grok/* branch. Returns branch + diffstat. No push, no merge, no --always-approve. Dev-only — not the product admin-bridge. |
| grok_delegate_planA | Read-only plan variant of grok_delegate (plan_only=true). Does not allow write/edit/shell mutation in the permission profile. |
| grok_delegate_startA | Start grok_delegate in the BACKGROUND and return a job_id immediately. Use this instead of grok_delegate for real lanes: a lane runs for minutes and a synchronous call is killed by the client timeout, leaving an empty worktree. Poll with grok_delegate_poll. Same guarded profile, no push, no merge. |
| grok_delegate_pollA | Poll a background delegation started with grok_delegate_start. With job_id: that job's state and result (branch, changed_files, commits, diffstat), plus live progress while running — phase (preflight/worktree/worktree_recover/anchors/executor/collect), elapsed_s, phase_elapsed_s, last_step, and worker_pid once the executor is spawned. A dispatch spends its first minutes in git with no process and no lane directory to see: that is normal, and phase is how you tell it apart from a stuck server. Without job_id: newest job summaries. Read-only. |
| grok_delegate_statusA | Structured health status: grok binary/version, auth presence (without reading auth.json), git availability, allowed roots/lanes_parent, permission and sandbox profile info. Read-only. |
| grok_delegate_doctorA | Run |
| grok_delegate_modelsA | List available models via |
| grok_delegate_inspectA | Run |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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/zai-one/grok-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server