@runapi.ai/luma-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Your RunAPI API key. Can also be set via config file at ~/.config/runapi/config.json. |
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": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json. |
| modify_videoB | Create a Luma task on RunAPI (modify video). Returns a task id, status, and output URLs. |
| get_taskA | Fetch the current status and latest result payload for a luma task. |
| check_pricingA | Look up RunAPI pricing for the luma model line. |
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 4 tools
Each tool has a clear, distinct purpose: login handles authentication, modify_video creates a task, get_task retrieves task status, and check_pricing looks up rates. No two tools overlap in function.
All tool names follow a consistent snake_case verb_noun pattern (login, modify_video, get_task, check_pricing). The naming is predictable and uniform.
With 4 tools, the server is well-scoped for its purpose—covering authentication, task creation, status polling, and pricing. The count is neither excessive nor too sparse.
The core workflow of log in, modify a video, and check task status is fully covered, with pricing lookup as a bonus. Minor gaps like listing or canceling tasks exist, but they aren't essential for the primary use case.