A
licenseB
qualityA
maintenanceMCP server for Veo 3.1 video generation models, enabling task creation (extend, text-to-video, upscale), status polling, and pricing checks via RunAPI.
6
46 npm
1
Apache 2.0
@runapi.ai/gemini-omni-mcp
by runapi-ai
Related Servers
Alternatives to @runapi.ai/gemini-omni-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for the InfiniteTalk model line, enabling audio-to-video task creation, status polling, and pricing checks via a RunAPI API key.428 npmApache 2.0
- AlicenseAqualityAmaintenanceMCP server for GPT-4o Image model line, enabling text-to-image task creation, status polling, and pricing checks via RunAPI.472 npmApache 2.0
- AlicenseBqualityAmaintenanceMCP server for the Wan model line enabling AI-driven animation, video editing, and image/video generation tasks via RunAPI with status polling and pricing.925 npmApache 2.0
- AlicenseAqualityAmaintenanceRunAPI MCP server for the Imagen 4 model line. Create tasks, poll their status, and check pricing through a single RunAPI API key.526 npmApache 2.0
- AlicenseAqualityAmaintenanceMCP server for the Runway Aleph model line. Enables creating edit video tasks, polling status, and checking pricing through a single RunAPI API key.436 npmApache 2.0
TDQS
A3.7/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct operation: video creation, character creation, audio creation, pricing lookup, task status fetch, and authentication. There is no ambiguity between them, as the action and resource are clearly separated.
Naming Consistency4/5
Most tools follow a verb_noun pattern (create_character, create_audio, check_pricing, get_task), but text_to_video is a descriptive noun phrase rather than a verb, and login is a single verb. These minor deviations are still readable and predictable overall.
Tool Count5/5
With 6 tools, the server is well-scoped for a media generation API. It covers creation, status tracking, pricing, and authentication without unnecessary bloat or redundancy.
Completeness4/5
The tool surface covers the core lifecycle: creating various media types, retrieving task results, checking pricing, and authenticating. Missing operations like list/cancel tasks or delete resources are plausible gaps but not critical for typical usage, so the coverage is largely sufficient.
Maintenance
ActivityMaintained
ResponsivenessNo issues