Maestro MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACEDATACLOUD_API_TOKEN | Yes | Your Ace Data Cloud API token. Get one from https://platform.acedata.cloud/console/applications |
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 |
|---|---|
| maestro_get_taskA | Get live progress and final outputs for one Maestro video task. |
| maestro_list_tasksA | List recent Maestro tasks owned by the authenticated user. |
| maestro_create_videoA | Create a complete video or iterate on a prior Maestro video. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| maestro_video_workflow | Explain the recommended Maestro workflow. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool covers a distinct operation: listing tasks, creating a video, and retrieving task status/outputs. There is no overlap between creating, listing, and fetching a single task.
All tool names follow the same verb_noun pattern with snake_case: list_tasks, create_video, get_task. The naming is uniform and predictable across the set.
Three tools is a minimal but valid set for the video creation workflow. The count is slightly low, but each tool is necessary for the core create-monitor-retrieve flow.
The surface covers the full lifecycle for a video task: create, list, and get results. Minor gaps exist such as cancel/delete or updating task parameters, but the primary workflow is fully supported.