xAI Grok MCP Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAI_API_KEY | No | Optional API key for authentication with x.ai, used if not logged in via grok login | |
| GROK_CLI_PATH | No | Optional path to the grok CLI executable if not on PATH |
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_askB | Ask Grok a prompt in a new headless CLI session. |
| grok_continueC | Continue a Grok headless session. If |
| grok_code_reviewA | Ask Grok for a strict second-opinion code review. This tool is intended to run after CodeHelper or manual analysis. It sends
strict run-scoped review rules, disables web search, and passes large
prompts via |
| grok_versionA | Return the installed Grok CLI version. |
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 4 tools
Each tool has a distinct purpose: general prompting, code review, session continuation, and version checking. No overlap in functionality.
All tools follow a consistent pattern: 'grok_' prefix with snake_case verb or noun suffixes (ask, code_review, continue, version).
4 tools is on the lower end but still appropriate for a focused bridge to a CLI tool. Could be expanded slightly but not under-scoped.
Core operations are covered: prompting, code review, session continuation, and version info. Missing session management or configuration tools but minimal for the domain.