LumaMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | INFO |
| LUMA_REQUEST_TIMEOUT | No | Request timeout in seconds | 1800 |
| ACEDATACLOUD_API_TOKEN | Yes | API token from AceDataCloud (Required) | |
| ACEDATACLOUD_API_BASE_URL | No | API base URL | https://api.acedata.cloud |
| LUMA_DEFAULT_ASPECT_RATIO | No | Default aspect ratio | 16:9 |
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 |
|---|---|
| luma_list_aspect_ratiosA | List all available aspect ratios for Luma video generation. |
| luma_list_actionsA | List all available Luma API actions and corresponding tools. |
| luma_get_taskA | Query the status and result of a video generation task. |
| luma_get_tasks_batchA | Query multiple video generation tasks at once. |
| luma_generate_videoA | Generate AI video from a text prompt using Luma Dream Machine. |
| luma_generate_video_from_imageA | Generate AI video using reference images as start and/or end frames. |
| luma_extend_videoA | Extend an existing video with additional content. |
| luma_extend_video_from_urlA | Extend an existing video using its URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| luma_video_generation_guide | Guide for choosing the right Luma tool for video generation. |
| luma_workflow_examples | Common workflow examples for Luma video generation. |
| luma_prompt_suggestions | Prompt writing suggestions for Luma video generation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools are clearly distinct: generation, image-based generation, status checks, and aspect ratio listing are unambiguous. The only potential confusion is luma_extend_video vs luma_extend_video_from_url, which perform the same operation but differ by input identifier; descriptions help but the overlap could still cause misselection.
All tools follow a consistent luma_<verb>_<object> snake_case pattern. Verbs are predictable (list, get, generate, extend) and names clearly map to their actions, making the set easy to navigate.
Eight tools is well-scoped for a video generation MCP server. Each tool earns its place, covering discovery, generation, extension, and status retrieval without unnecessary redundancy or bloat.
The core video generation lifecycle is covered: generate text-to-video, generate from images, extend videos, and query task status individually or in batch. Minor gaps exist, such as no cancellation or listing of all past tasks, but these are not critical to the primary workflow.