Runway API MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TOOL_TIMEOUT | No | Timeout for MCP tools in milliseconds | 1000000 |
| RUNWAYML_API_SECRET | Yes | Your Runway 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| runway_generateVideoA | Generate a video from an image and a text prompt. Accepted ratios are 1280:720, 720:1280, 1104:832, 832:1104, 960:960, 1584:672. Use 1280:720 by default. For duration, there are only either 5 or 10 seconds. Use 5 seconds by default. If the user asks to generate a video, always first use generateImage to generate an image first, then use the image to generate a video. |
| runway_generateImageA | Generate an image from a text prompt and optional reference images. Available ratios are 1920:1080, 1080:1920, 1024:1024, 1360:768, 1080:1080, 1168:880, 1440:1080, 1080:1440, 1808:768, 2112:912, 1280:720, 720:1280, 720:720, 960:720, 720:960, 1680:720. Use 1920:1080 by default. It also accepts reference images, in the form of either a url or a base64 encoded image. Each reference image has a tag, which is a string that refers to the image from the user prompt. For example, if the user prompt is "IMG_1 on a red background", and the reference image has the tag "IMG_1", the model will use that reference image to generate the image. The return of this function will contain a url to the generated image. |
| runway_upscaleVideoC | Upscale a video to a higher resolution. videoUri takes in a url of a video or a data uri of a video. |
| runway_editVideoB | Edit a video using Runway Aleph. promptText is a prompt for the video. videoUri takes in a url of a video or a data uri of a video. Accepted Ratio values are 1280:720, 720:1280, 1104:832, 960:960, 832:1104, 1584:672, 848:480, 640:480. Use 1280:720 by default. It also accepts reference images, in the form of either a url or a base64 encoded image. Each reference image has a tag, which is a string that refers to the image from the user prompt. For example, if the user prompt is "IMG_1 on a red background", and the reference image has the tag "IMG_1", the model will use that reference image to generate the image. |
| runway_getTaskA | Get the details of a task, if the task status is 'SUCCEEDED', there will be a 'url' field in the response. If the task status is 'FAILED', there will be a 'error' field in the response. If the task status is 'PENDING' or 'RUNNING', you can call this tool again in 5 seconds to get the task details. |
| runway_cancelTaskC | Deletes or cancels a given task. |
| runway_getOrgB | Returns details like credit balance, usage details, and organization information. |
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 7 tools
Each tool has a clearly distinct purpose: cancelTask, editVideo, generateImage, generateVideo, getOrg, getTask, and upscaleVideo. There is no overlap in functionality; for example, generateImage and generateVideo serve different media types, and getTask and cancelTask manage tasks distinctly. The descriptions reinforce these distinctions, making misselection unlikely.
All tools follow a consistent snake_case naming pattern with the prefix 'runway_' followed by a verb_noun structure (e.g., runway_cancelTask, runway_generateImage). This uniformity makes the tool set predictable and easy to navigate, with no deviations in style or convention.
With 7 tools, the server is well-scoped for a video and image generation API. Each tool serves a specific, necessary function—covering task management, media generation, editing, upscaling, and organization details—without being overly sparse or bloated. The count aligns perfectly with the domain's typical operations.
The tool set covers core workflows for video and image generation, including create (generateImage/generateVideo), read (getTask/getOrg), update (editVideo/upscaleVideo), and delete (cancelTask). A minor gap is the lack of a tool for deleting or managing generated media files, but agents can work around this using existing tools for task cancellation and retrieval.