@runapi.ai/runway-aleph-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Your RunAPI API key. Alternatively, can be set in ~/.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. |
| edit_videoB | Create a Runway Aleph task on RunAPI (edit video). Returns a task id, status, and output URLs. |
| get_taskB | Fetch the current status and latest result payload for a runway-aleph task. |
| check_pricingB | Look up RunAPI pricing for the runway-aleph 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 distinct action and resource: login (auth), edit_video (create task), get_task (poll task), and check_pricing (billing info). There is no meaningful overlap, so an agent can select the right tool unambiguously.
Three tools follow a clean verb_noun pattern (edit_video, get_task, check_pricing), while login uses only a verb with no noun. This is a minor deviation but the set remains readable and predictable.
Four tools cover the minimal lifecycle of auth, task creation, task polling, and pricing lookup. It is slightly lean but still reasonable for a narrowly scoped async video-editing API, with no redundant tools.
The core create-and-poll workflow is present, but notable task-management operations like cancel_task, list_tasks, or fetching/exporting output assets are missing. Agents can complete basic edits but lack lifecycle control beyond polling and no way to clean up or browse tasks.