grok-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAI_API_KEY | No | Optional authentication method when supported by the local Grok CLI. | |
| GROK_BRIDGE_HOME | No | Directory for bridge jobs and bounded logs. | ~/.grok/bridge |
| GROK_BRIDGE_GROK_EXE | No | Absolute path or command name for the Grok executable. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| grok_doctorA | Check whether Grok Build, local authentication, the bridge runtime, and xhigh defaults are ready. |
| grok_consultA | Run a synchronous, read-only Grok second opinion for planning, research, analysis, or code review. Uses xhigh reasoning by default and cannot edit files. |
| grok_startA | Start a durable background Grok job for implementation, debugging, testing, or review. It may edit files and run commands inside cwd. Poll the returned job_id until terminal. |
| grok_pollA | Read a background Grok job's state, final result, and bounded log tails. Continue polling while state is queued or running. |
| grok_cancelA | Cancel one known Grok Bridge background job and its child process tree. |
| grok_listB | List recent bridge jobs plus Grok's local session index, useful for resuming work across ChatGPT sessions. |
| grok_export_sessionA | Export a Grok session transcript as Markdown so another ChatGPT session can inspect prior delegated work. |
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 7 tools
Each tool has a distinct, non-overlapping purpose: health check, synchronous consult, async job lifecycle (start/poll/cancel), listing, and session export. No two tools could be confused for one another.
All tools share the consistent grok_ prefix and use clear, action-oriented snake_case names. While some are simple verbs (grok_start) and others verb-noun (grok_export_session), the pattern is uniform and predictable.
Seven tools is well-scoped for a bridge server dedicated to Grok integration. Each tool covers a necessary operation without bloat or redundancy.
The tool set covers the full lifecycle: readiness check, synchronous consultation, background job management (start, poll, cancel), history listing, and session export. No obvious gaps for the domain.