VeoMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | INFO |
| VEO_DEFAULT_MODEL | No | Default model for generation | veo2 |
| VEO_REQUEST_TIMEOUT | No | Request timeout in seconds | 180 |
| ACEDATACLOUD_API_TOKEN | Yes | API token from AceDataCloud | |
| ACEDATACLOUD_API_BASE_URL | No | API base URL | https://api.acedata.cloud |
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 |
|---|---|
| veo_list_modelsA | List all available Veo models and their capabilities. |
| veo_list_actionsA | List all available Veo API actions and corresponding tools. |
| veo_get_prompt_guideA | Get guidance on writing effective prompts for Veo video generation. |
| veo_get_taskA | Query the status and result of a video generation task. |
| veo_get_tasks_batchA | Query multiple video generation tasks at once. |
| veo_text_to_videoA | Generate AI video from a text prompt using Veo. |
| veo_image_to_videoA | Generate AI video from one or more reference images using Veo. |
| veo_get_1080pA | Get the 1080p high-resolution version of a generated video. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| veo_video_generation_guide | Guide for choosing the right Veo tool for video generation. |
| veo_workflow_examples | Common workflow examples for Veo video generation. |
| veo_style_suggestions | Style and prompt writing suggestions for Veo. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have distinct purposes (text-to-video, image-to-video, status checking), but veo_get_task and veo_get_tasks_batch overlap slightly in that both retrieve task status, just for different counts. Descriptions clarify the difference, so ambiguity is minimal.
All tools follow a consistent 'veo_<verb>_<noun>' pattern (e.g., veo_get_task, veo_list_models, veo_text_to_video). The verbs are descriptive and the pattern is uniform across all 8 tools.
With 8 tools, the server is well-scoped for a video generation MCP. Each tool addresses a core need: generation (text/image), task management (single/batch), model/prompt guidance, and resolution upgrade. No bloat or sparseness.
The tool set covers the core lifecycle: create (text/image), poll status (single/batch), and retrieve high-res output. A minor gap is no explicit cancellation or deletion tool for tasks, but that may not be critical for the domain.