pmind-veo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VEO_MODEL | Yes | Default Veo model (must be full API name): veo-2.0-generate-001, veo-3.0-generate-preview, or veo-3.0-fast-generate-preview | |
| CONFIG_DIR | No | Directory for state files and downloads (default: ~/.pmind-veo-mcp) | |
| GEMINI_API_KEY | Yes | Your Gemini API key with video generation access |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| veo_generate_videoA | Generate videos using Google's Veo models. Supports:
This tool starts a background video generation process that:
To download generated videos, use veo_download_video after generation completes. Returns:
Examples: Text-to-video: "Serene waterfall in a lush forest, cinematic lighting" Image-to-video: Use image_path="/path/to/image.jpg" with optional prompt |
| veo_check_generationA | Check the status of a video generation subprocess. This monitors the subprocess that is handling the video generation, not the Gemini API directly. The subprocess handles all API polling. If the generation has an operation_id, you can also use veo_check_operation to directly query Google's API for the operation status. |
| veo_list_generationsA | List all video generation sessions. Shows all subprocess-based generation sessions with their current status. |
| veo_list_sessionsB | List all video generation sessions. Shows all subprocess-based generation sessions with their current status. |
| veo_cleanup_sessionsA | Clean up old generation sessions and their files. Removes state files and optionally downloaded videos for old sessions. |
| veo_download_videoA | Download a generated video from a completed generation session. Use this tool to:
Note: Due to current SDK limitations, this downloads placeholder data. The actual video generation API requires allowlist access. Returns:
|
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 6 tools
The tools are mostly distinct, but veo_list_generations and veo_list_sessions have identical descriptions, making them impossible to differentiate. This redundancy creates clear ambiguity for an agent selecting which to use.
All six tools follow the veo_verb_noun pattern consistently, with clear verbs like generate, check, list, cleanup, and download. There is no mixing of styles or vague naming.
With six tools, the server is well-scoped for video generation workflows. The count covers generation, status checking, listing, downloading, and cleanup without being excessive or thin.
The core lifecycle (generate, check, list, download, cleanup) is covered, but there is no cancel/delete operation, and the description mentions veo_check_operation which is not actually exposed. These gaps could frustrate agents needing abort or granular API status.