Grok Membership Media MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| media_doctorA | Check Grok.com membership login, strict API-key disable policy, ChatGPT browser membership readiness, FFmpeg, state storage, and allowed roots. Does not generate media. |
| start_website_videoB | Start an asynchronous website video job using only paid ChatGPT/Grok membership sessions. GPT browser creates the first frame when available; Grok membership image_gen is the safe pre-submit fallback; Grok membership image_to_video creates the MP4. Returns immediately with a job_id. |
| get_media_jobA | Return the current status and verified output paths for one media job. |
| list_media_jobsB | List recent membership media jobs without starting any generation. |
| cancel_media_jobA | Stop the local worker for a queued/running job. If Grok already received the media tool call, upstream quota consumption may continue; the job is marked cancelled_local or submitted_unknown and is never auto-retried. |
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 5 tools
Each tool has a distinct purpose: cancel, get, list, diagnose, and start. While get_media_job and list_media_jobs both retrieve job info, they are clearly differentiated by specificity. No two tools are easily confused.
Four tools follow a consistent verb_noun pattern (cancel_media_job, get_media_job, list_media_jobs, start_website_video). media_doctor breaks this pattern with a noun_verb structure, causing minor inconsistency.
With 5 tools, the server is well-scoped for its purpose of managing media jobs. It covers essential operations without being bloated or too sparse.
The tool set covers core operations: start, list, get, cancel, and diagnostic check. Minor gaps like updating or retrying jobs are not critical for the primary workflow, making it nearly complete.