runway-mcp
Related Servers
Alternatives to runway-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables creating and polling Luma video modification tasks, fetching task status, and checking pricing via the RunAPI API.464 npmApache 2.0

Runway API MCP Serverofficial
AlicenseAqualityFmaintenanceEnables AI video and image generation through the Runway API. Supports video generation from images and text prompts, image creation, video upscaling and editing, and task management.711 npm23MIT- AlicenseAqualityAmaintenanceEnables AI image and video generation tasks (text-to-image, image-to-video, edit, upscale, etc.) via RunAPI, with support for polling and pricing lookups.10120 npm1Apache 2.0
- AlicenseAqualityAmaintenanceEnables creating text-to-video tasks using Seedance models, polling task status, and checking pricing via a single RunAPI API key.482 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables creating and managing HappyHorse video generation tasks (edit, image-to-video, text-to-video) via RunAPI, with optional polling for completion and pricing lookup.675 npmApache 2.0
- AlicenseBqualityAmaintenanceEnables interaction with Kling AI models for video generation and avatar tasks via RunAPI, including task creation, status polling, and pricing checks.9136 npmApache 2.0
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.