@runapi.ai/luma-mcp
Related Servers
Alternatives to @runapi.ai/luma-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables creating and managing Runway video generation tasks (text-to-video, video extension) through a single RunAPI key, including task polling and pricing checks.5273 npmApache 2.0
- 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.10268 npm1Apache 2.0
- AlicenseBqualityAmaintenanceEnables interaction with Kling AI models for video generation and avatar tasks via RunAPI, including task creation, status polling, and pricing checks.9187 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.6266 npmApache 2.0
- AlicenseAqualityAmaintenanceEnables creating text-to-video tasks using Seedance models, polling task status, and checking pricing via a single RunAPI API key.4278 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.722 npm23MIT
TDQS
Scored across 4 tools
Each tool targets a clearly distinct concern: authentication (login), task creation (modify_video), task polling (get_task), and pricing lookup (check_pricing). There is no overlap in purpose, so an agent can select correctly without hesitation.
Three of four tools follow a clean verb_noun snake_case pattern (modify_video, get_task, check_pricing). The lone outlier 'login' uses a bare verb rather than verb_object, which is a minor but forgivable deviation.
Four tools is reasonable for a narrowly scoped wrapper around a single Luma model line, and each tool serves a purpose. It leans slightly thin, since only one tool actually performs the core operation.
The surface covers auth, task creation, status polling, and pricing, but omits obvious lifecycle operations such as canceling a task, listing tasks, or other Luma video operations (e.g. generate/extend). Agents hitting these needs would be stuck with no tool to call.