@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. |
| 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 3 tools
The three tools have clearly distinct purposes: pricing lookup, task status retrieval, and authentication. There is no overlap or realistic chance of an agent confusing one for another.
check_pricing and get_task follow a consistent verb_noun snake_case pattern, and login is also snake_case but is a bare verb with no noun. The minor deviation is conventional and still readable.
Three tools is borderline thin for a model-serving MCP; one slot is consumed by login and another by pricing, leaving only a single task-status tool. A minimal client could work with this, but it feels under-scoped.
The surface has a major dead end: get_task retrieves results but no tool submits or creates a Luma task, so the core generate/run workflow cannot be initiated. Pricing and login are covered, but the primary lifecycle operation is missing.