grok-video-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAI_API_KEY | Yes | xAI API key | |
| GROK_VIDEO_MODEL | No | Model (grok-imagine-video-1.5 = 1080p) | grok-imagine-video |
| GROK_VIDEO_OUTPUT_DIR | No | Where clips are saved | ~/.grok-video-mcp/output |
| GROK_VIDEO_TIMEOUT_MS | No | Max wait for a generation | 900000 |
| GROK_VIDEO_POLL_MAX_MS | No | Max poll interval (×1.5 backoff) | 30000 |
| GROK_VIDEO_POLL_BASE_MS | No | Initial poll interval | 5000 |
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 |
|---|---|
| generate_videoA | Submit a Grok video generation from a text prompt. Returns a requestId to poll with get_generation and download with get_video. Generation takes 1-5 minutes. ~$0.005/sec. |
| get_generationA | Poll the status of a Grok video generation by requestId. Returns PENDING, COMPLETED, or FAILED with progress when available. |
| get_videoA | Download a completed Grok video generation to disk. Returns the file path. Requires the generation to be COMPLETED. |
| generate_and_waitA | Submit a Grok video generation, poll until complete (up to timeoutSeconds), and return the downloaded file path. The one-call convenience for agents. |
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 clear, distinct role: generate_video submits, get_generation polls status, get_video downloads, and generate_and_wait combines these steps. The purpose of each is unambiguous, even with the convenience wrapper.
Most tools follow a clear verb_noun pattern (generate_video, get_generation, get_video). generate_and_wait deviates with a compound verb phrase, but the style is still consistent and readable.
Four tools is ideal for a focused video generation service: submit, poll, download, and a convenience flow. Each tool earns its place without bloat.
The tool surface covers the full lifecycle of video generation: submit, check status, retrieve result, and a one-call convenience. No obvious gaps remain for the stated purpose.