grok-cookie-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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| imagine_agent_startB | Start a Grok Imagine Agent conversation and send the first prompt. |
| imagine_agent_sendC | Send a follow-up prompt to an existing Grok Imagine Agent conversation. |
| imagine_agent_readC | Read responses from a Grok Imagine Agent conversation. |
| generate_imageC | Generate images through the working Grok media endpoint and return parsed image URLs. |
| generate_videoC | Generate video through the working Grok media endpoint and return parsed video URLs. |
| image_to_videoC | Create or reuse an image post, then generate a video from it. |
| create_media_postC | Create a Grok media post from mediaType/prompt/mediaUrl. |
| create_share_linkC | Create a share link for a Grok media post. |
| upscale_videoC | Ask Grok to upscale a generated video by video_id. |
| check_quotaB | Return Grok Imagine quota_info. |
| upload_local_fileA | Upload a local file to Grok storage via /http/upload-file-v2/direct. Returns fileMetadataId to use as @reference in a follow-up chat message. |
| list_accountsB | List Grok accounts available in cookies/.json. |
| send_to_telegramA | Download a Grok media post by post_id using account cookies and send it to Telegram as video/photo. |
| list_projectsB | List Grok Imagine projects (canvases) for the account. |
| create_projectB | Create a new Grok Imagine project (canvas). |
| get_project_conversationsC | List agent conversations attached to a project. |
| create_project_nodeC | Attach a node (media post) to a project canvas. |
| set_project_thumbnailC | Set the thumbnail post for a project. |
| list_templatesB | List Grok Imagine pipeline templates (Short Film, UGC Product Stories, etc.). |
| get_templateA | Get a Grok Imagine template summary by templateId. |
| list_foldersC | List Grok Imagine folders. |
| get_post_foldersC | List folders that a post belongs to. |
| list_postsC | List Grok Imagine posts owned or liked by the account. |
| list_project_postsB | Get a Grok project canvas (nodes + attached posts). |
| get_postB | Get a Grok media post by post_id. |
| like_postC | Like a Grok media post. |
| delete_postC | Delete a Grok media post. |
| search_statusC | Return Grok Imagine media search index status. |
| agent_startC | Start Grok Imagine Agent conversation (optionally inside a project). |
| agent_sendC | Send a follow-up prompt to a Grok Imagine Agent conversation. |
| agent_readC | Load recent responses of a Grok Imagine Agent conversation. |
| plan_seriesC | Ask Grok to plan a video series (episodes + scenes + prompts) and save it to series/.json. |
| list_seriesA | List series files stored in series/*.json. |
| get_seriesC | Return the full series JSON by id. |
| update_sceneC | Update fields on a specific scene (status, prompt, aspect_ratio, video_url, ...). |
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 35 tools
Multiple tools have overlapping purposes, notably the 'agent_' and 'imagine_agent_' pairs (read, send, start) which are nearly identical. Additionally, 'generate_image' and 'generate_video' are distinct but 'image_to_video' combines both functions, creating ambiguity. An agent would struggle to choose correctly between these similar tools.
Tool names mostly follow a verb_noun pattern in snake_case, but there are inconsistencies: 'create_media_post' vs 'delete_post' (missing 'media'), 'send_to_telegram' (preposition), and the redundant 'agent_' vs 'imagine_agent_' prefixes. The naming is functional but not fully predictable.
35 tools is above the typical well-scoped range (3-15), making the surface feel heavy. While the domain (Grok Imagine) is complex and may justify many tools, several are redundant (e.g., agent vs imagine_agent), suggesting the count could be reduced without losing capability.
The tool set covers core CRUD operations for posts, projects, agents, and series, plus media generation, sharing, and Telegram integration. Minor gaps exist, such as no 'update_post' tool (only delete and get) and no tool to manage user settings, but the surface is largely sufficient for the domain.