grok-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GC_DEBUG | No | Enable debug mode (e.g., 'true' or 'false') | false |
| GC_COMPACT | No | Compact handoff mode: short stdout + handoff path | |
| GC_DEBUG_GUI | No | Open a native pywebview debug window | |
| GC_LOG_DEBUG | No | Enable full subprocess debug logging | |
| GC_REPO_ROOT | Yes | Path to the grok-and-claude checkout that has bin/ and .team/ | |
| GC_DEBUG_OPEN | No | Never open browser (set to '0' to disable) | |
| GC_SIGINT_MODE | No | SIGINT handling: 'cancel' or 'cancel_then_exit' | cancel |
| GC_DEBUG_WINDOW | No | Use a browser tab instead of native window (set to '0' to fall back) | |
| GC_BRIDGE_DEBUG_DIR | No | Directory for debug logs | /tmp/grok-bridge-debug |
| GC_DEBUG_FORCE_OPEN | No | Force opening a debug window/tab | |
| GC_DEBUG_IDLE_TIMEOUT | No | Idle timeout in seconds before auto-closing the debug window | 15 |
| GC_FIRST_EVENT_TIMEOUT | No | Timeout in seconds for the first output event | 45 |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| grok_askA | Ask Grok (consult by default; worker=True to let Grok edit/run shell in cwd).
Returns JSON: {"status","class","text","run_id","handoff","cwd"} status is SUCCESS | FAILED(class) | TIMEOUT; text is the reply body. |
| grok_workflowA | Run a named Grok Build workflow (e.g. audit-plan, verify-diff).
Returns JSON: {"workflow","success","summary","run_id","handoff"} |
| grok_workflowsA | List available Grok Build workflows (from .grok/workflows/*.rhai). |
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/Dragonshock/cli-agent-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server