A
licenseB
qualityB
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
516 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
- AlicenseBqualityBmaintenanceMCP server for the InfiniteTalk model line, enabling audio-to-video task creation, status polling, and pricing checks via a RunAPI API key.4232 npm1Apache 2.0
- AlicenseBqualityBmaintenanceMCP server for GPT-4o Image model line, enabling text-to-image task creation, status polling, and pricing checks via RunAPI.4272 npmApache 2.0
- AlicenseBqualityBmaintenanceMCP server for the Wan model line enabling AI-driven animation, video editing, and image/video generation tasks via RunAPI with status polling and pricing.970 npmApache 2.0
- AlicenseAqualityBmaintenanceRunAPI MCP server for the Imagen 4 model line. Create tasks, poll their status, and check pricing through a single RunAPI API key.5216 npmApache 2.0
- AlicenseBqualityBmaintenanceMCP server for the Runway Aleph model line. Enables creating edit video tasks, polling status, and checking pricing through a single RunAPI API key.3252 npmApache 2.0
TDQS
B3.2/5.0
Scored across 6 tools
Disambiguation4/5
Each tool targets a fairly distinct action (auth, pricing lookup, task polling, and three generation endpoints), so an agent can mostly pick correctly. The main blur is between the synchronous create_character/create_audio operations and the task-based text_to_video + get_task flow, since it's unclear whether the sync creates also produce task ids that get_task can poll.
Naming Consistency3/5
Names mix three conventions: verb_noun (create_character, create_audio, get_task), verb_noun for a non-resource (check_pricing), a bare verb (login), and a noun-phrase endpoint name (text_to_video). It's still readable, but there is no single predictable pattern across all six.
Tool Count5/5
Six tools is well-scoped for a thin wrapper around one model line: auth, pricing, three generation entry points, and task polling. Nothing feels padded or redundant.
Completeness3/5
Core lifecycle is only partly covered: generation plus get_task exists, but there is no cancel_task, list_tasks, or bulk status retrieval, and login has no matching logout/config-status tool. The asymmetric model (two sync ops vs one async op) also leaves unclear how results of the sync operations are re-fetched.
Maintenance
ActivityMaintained
ResponsivenessNo issues