@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_videoC | Create a Luma task on RunAPI (modify video). Returns a task id, status, and output URLs. |
| get_taskB | Fetch the current status and latest result payload for a luma task. |
| check_pricingC | 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 targets a clearly distinct concern: authentication (login), task creation (modify_video), task polling (get_task), and pricing lookup (check_pricing). There is no overlap in purpose, so an agent can select correctly without hesitation.
Three of four tools follow a clean verb_noun snake_case pattern (modify_video, get_task, check_pricing). The lone outlier 'login' uses a bare verb rather than verb_object, which is a minor but forgivable deviation.
Four tools is reasonable for a narrowly scoped wrapper around a single Luma model line, and each tool serves a purpose. It leans slightly thin, since only one tool actually performs the core operation.
The surface covers auth, task creation, status polling, and pricing, but omits obvious lifecycle operations such as canceling a task, listing tasks, or other Luma video operations (e.g. generate/extend). Agents hitting these needs would be stuck with no tool to call.