Schema | grok-mcp

grok-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
grok_checkA	Probe whether Grok Build bridge + CLI are ready (node, grok binary, auth). Returns {rows: [{label, ok, detail}]} envelope; the raw bridge JSON is preserved in the 'bridge output' row's detail for callers that parsed the old shape.
grok_runA	Run a Grok Build task via bridge (`run`). background=true: bridge enqueues detached worker and exits; this tool only waits for that enqueue JSON (jobId), default max 60s — not the full agent run. Poll grok_show / report files for completion. write=false default (read-only). Prompt via --prompt-file under tmpdir. Foreground default timeout 900000ms (15 min). Pass cwd for project paths.
grok_runsC	List tracked Grok bridge runs, or one run by id (`runs`).
grok_showC	Show status/result of a Grok bridge run (`show`).
grok_stopC	Stop a running Grok bridge job (`stop`).
grok_bridge_pathA	Resolve which grok-bridge.mjs path this MCP server will use.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TuTouPower/grok-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server