@runapi.ai/luma-mcp
Related Servers
Alternatives to @runapi.ai/luma-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables creating and managing Runway video generation tasks (text-to-video, video extension) through a single RunAPI key, including task polling and pricing checks.5228 npmApache 2.0
- 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.10282 npm1Apache 2.0
- AlicenseBqualityBmaintenanceEnables interaction with Kling AI models for video generation and avatar tasks via RunAPI, including task creation, status polling, and pricing checks.9102 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.6261 npmApache 2.0
- AlicenseAqualityAmaintenanceEnables creating text-to-video tasks using Seedance models, polling task status, and checking pricing via a single RunAPI API key.4375 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.712 npm23MIT
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: pricing lookup, task status retrieval, and authentication. There is no overlap or realistic chance of an agent confusing one for another.
check_pricing and get_task follow a consistent verb_noun snake_case pattern, and login is also snake_case but is a bare verb with no noun. The minor deviation is conventional and still readable.
Three tools is borderline thin for a model-serving MCP; one slot is consumed by login and another by pricing, leaving only a single task-status tool. A minimal client could work with this, but it feels under-scoped.
The surface has a major dead end: get_task retrieves results but no tool submits or creates a Luma task, so the core generate/run workflow cannot be initiated. Pricing and login are covered, but the primary lifecycle operation is missing.