Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GC_DEBUGNoEnable debug mode (e.g., 'true' or 'false')false
GC_COMPACTNoCompact handoff mode: short stdout + handoff path
GC_DEBUG_GUINoOpen a native pywebview debug window
GC_LOG_DEBUGNoEnable full subprocess debug logging
GC_REPO_ROOTYesPath to the grok-and-claude checkout that has bin/ and .team/
GC_DEBUG_OPENNoNever open browser (set to '0' to disable)
GC_SIGINT_MODENoSIGINT handling: 'cancel' or 'cancel_then_exit'cancel
GC_DEBUG_WINDOWNoUse a browser tab instead of native window (set to '0' to fall back)
GC_BRIDGE_DEBUG_DIRNoDirectory for debug logs/tmp/grok-bridge-debug
GC_DEBUG_FORCE_OPENNoForce opening a debug window/tab
GC_DEBUG_IDLE_TIMEOUTNoIdle timeout in seconds before auto-closing the debug window15
GC_FIRST_EVENT_TIMEOUTNoTimeout in seconds for the first output event45

Capabilities

Features and capabilities supported by this server

CapabilityDetails
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

NameDescription
grok_askA

Ask Grok (consult by default; worker=True to let Grok edit/run shell in cwd).

  • prompt: the instruction to Grok (required)

  • channel: persistent conversation channel (default "default")

  • cwd: working directory (default: the repo root; worker mode requires a worktree/scratch — enforced by bin/grok-ask's own dual-gate)

  • worker: True = worker mode (write + shell, auto-approved; main tree refused unless dual-gate override)

  • model: grok model id (default grok-4.5)

  • attach_file: file path to attach into the prompt (repeatable not supported here)

  • timeout_secs: wall-clock timeout in seconds (0 = default)

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).

  • name: workflow name from .grok/workflows/ (list via grok_workflows)

  • args_json: JSON string of workflow args, e.g. '{"target":"HEAD"}'

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

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