runway-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Your RunAPI API key |
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. |
| extend_videoC | Create a Runway task on RunAPI (extend video). Returns a task id, status, and output URLs. |
| text_to_videoB | Create a Runway task on RunAPI (text to video). Returns a task id, status, and output URLs. |
| get_taskB | Fetch the current status and latest result payload for a runway task. |
| check_pricingB | Look up RunAPI pricing for the runway 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 5 tools
Each tool has a clearly distinct action and target: extend_video and text_to_video are separate generation modes, while get_task, check_pricing, and login serve unique supporting roles. No overlap in purpose is apparent from the descriptions.
Four of the five tools follow a verb_noun or verb_object pattern (extend_video, text_to_video, get_task, check_pricing). The lone login tool is a single verb, which is a minor but understandable deviation for an auth action.
Five tools is a well-scoped set for a focused Runway video-task integration, covering generation, status retrieval, pricing, and authentication without bloat. Each tool has a clear place in the workflow.
The surface covers task creation (two modes), status polling, pricing, and auth, but lacks obvious lifecycle operations such as cancel/delete task, list tasks, and other Runway generation modes like image-to-video. These are notable gaps for a server named after the broader Runway API.