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_videoA | Create a Runway task on RunAPI (text to video). Returns a task id, status, and output URLs. |
| get_taskA | Fetch the current status and latest result payload for a runway task. |
| check_pricingA | 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 distinct, non-overlapping purpose: authentication, video generation via two different input modes, task status retrieval, and pricing lookup. No two tools could be confused for one another.
Tool names follow a consistent lowercase_with_underscores pattern, predominantly verb_noun (extend_video, text_to_video, get_task, check_pricing). 'login' is a simple verb, but it fits the imperative style without deviating from the naming schema.
With 5 tools, the server is well-scoped for its purpose: authentication, generation, status checking, and pricing. This is neither too sparse nor too heavy, covering the core workflow without unnecessary clutter.
The core lifecycle is covered: create a generation task (two types), query its status, and retrieve output. Minor gaps include lack of a task listing or cancellation tool, but these are not essential to the primary generate-and-poll workflow.