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

Runway API MCP Serverofficial
AlicenseAqualityBmaintenanceEnables 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.77 npm22MIT- AlicenseBqualityAmaintenanceEnables AI image and video generation tasks (text-to-image, image-to-video, edit, upscale, etc.) via RunAPI, with support for polling and pricing lookups.1091 npmApache 2.0
- AlicenseAqualityAmaintenanceEnables creating text-to-video tasks using Seedance models, polling task status, and checking pricing via a single RunAPI API key.479 npmApache 2.0
- AlicenseAqualityAmaintenanceEnables creating and managing HappyHorse video generation tasks (edit, image-to-video, text-to-video) via RunAPI, with optional polling for completion and pricing lookup.643 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.841 npmApache 2.0
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.