What can you do with this server?

This MCP server provides focused access to Gemini Omni models via RunAPI, enabling AI agents to create multimodal generation tasks, poll task results, and check pricing. * create_audio: Generate audio content using the gemini-omni-audio model, with optional polling until completion. * create_character: Create a character image/asset using the gemini-omni-character model, supporting reference images and descriptions. * text_to_video: Convert text prompts into videos using the gemini-omni-text-to-video model, with configurable duration (4, 6, 8, or 10 seconds), aspect ratio (16:9 or 9:16), and resolution (720p, 1080p, or 4K). * get_task: Poll the status and retrieve output URLs for any previously created task using its ID and original endpoint. * check_pricing: Look up current pricing for any Gemini Omni model/endpoint combination — no API key required. Task execution can either wait for completion (polling) or return immediately with a task ID for asynchronous handling. A RUNAPI_API_KEY is required for creating and polling tasks. Compatible with Claude Code, Codex, Cursor, Windsurf, VS Code, Roo Code, and other MCP-compatible hosts.

How do I use @runapi.ai/gemini-omni-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@runapi.ai/gemini-omni-mcp Create an audio task with the text 'Hello'" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

@runapi.ai/gemini-omni-mcp

by runapi-ai

Overview Schema Source Related Servers Score Discussions Admin

TypeScript

Remote

Why This Package?

@runapi.ai/gemini-omni-mcp is a focused Model Context Protocol server for the Gemini Omni model line on RunAPI. It gives MCP-compatible assistants direct access to 3 endpoints and 4 model variants without loading the full RunAPI catalog.

Use this per-model server when an agent should stay scoped to Gemini Omni. Use @runapi.ai/mcp when one assistant should discover every RunAPI model line.

Related MCP server: imagen-4-mcp

Install

Add it to Claude Code:

claude mcp add gemini-omni -s user -- npx -y @runapi.ai/gemini-omni-mcp

Use project scope when the server should be shared with a repository:

claude mcp add gemini-omni -s project -- npx -y @runapi.ai/gemini-omni-mcp

Codex, Cursor, Windsurf, VS Code, Roo Code, and other MCP hosts can use the same stdio command:

{
  "mcpServers": {
    "gemini-omni": {
      "command": "npx",
      "args": ["-y", "@runapi.ai/gemini-omni-mcp"]
    }
  }
}

check_pricing works before sign-in. For task creation and status polling, ask your assistant to call the login tool. It opens a browser login and saves credentials to ~/.config/runapi/config.json, the same file used by runapi login. Headless and CI hosts can still set RUNAPI_API_KEY before starting the MCP host.

Ready-made examples are in examples/ for Claude, Cursor, Windsurf, VS Code, and Roo Code.

Tools

Tool	Auth	Purpose
`create_audio`	Yes	Run a Gemini Omni create audio operation synchronously. Returns the operation result.
`create_character`	Yes	Run a Gemini Omni create character operation synchronously. Returns the operation result.
`text_to_video`	Yes	Create a Gemini Omni text to video task and optionally wait for a terminal status. Returns the task id, status, and output URLs.
`get_task`	Yes	Fetch the current status and latest payload for an existing task.
`check_pricing`	No	Look up current pricing for a Gemini Omni model and endpoint.

Models

Gemini Omni covers 4 model variants across 3 endpoints. Each tool accepts the models listed for it:

Tool	Models
`create_audio`	`gemini-omni-audio`
`create_character`	`gemini-omni-character`
`text_to_video`	`gemini-omni-flash-preview`, `gemini-omni-text-to-video`

Model availability can change between releases. Use check_pricing or the Gemini Omni model page for the current catalog view.

Agent Prompts

Ask your assistant in natural language; it can inspect pricing, create the task, and return the task id plus output URLs.

Create a task

Run a Gemini Omni text to video task with RunAPI.

The assistant can call check_pricing, then text_to_video, and return the task id, status, and output URLs.

Submit without waiting

Create the task but don't wait for it to finish.

The assistant calls the create tool with wait: false and returns the task id. Check on it later with get_task.

Check pricing before creating

Check current Gemini Omni pricing, then create the task if it matches my request.

The assistant calls check_pricing and can link to the Gemini Omni model page for the canonical catalog entry.

Configuration

The server resolves auth in this order:

RUNAPI_API_KEY environment variable, useful for headless and CI hosts
~/.config/runapi/config.json, created by the MCP login tool or runapi login
No key, which still allows check_pricing

The config file is normally managed by login. A pre-provisioned headless config can use:

{
  "apiKey": "your_runapi_key"
}

Do not commit real API keys.

Links

Resource	URL
Gemini Omni model page	https://runapi.ai/models/gemini-omni
npm package	@runapi.ai/gemini-omni-mcp
GitHub repository	runapi-ai/gemini-omni-mcp
RunAPI MCP overview	runapi.ai/mcp
RunAPI docs	runapi.ai/docs

License

Licensed under the Apache License, Version 2.0.

Available Tools

6 tools

check_pricingA

Look up RunAPI pricing for the gemini-omni model line.

ParametersJSON Schema

Name	Required	Description	Default
`model`	No	Model slug. Defaults to the line's primary model.
`action`	No	Endpoint name. Defaults to the endpoint that offers the model.

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It implies a read-only operation via 'look up' but does not explicitly state that it has no side effects, whether authentication is required, or what exactly is returned. The description adds minimal behavioral context beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that is front-loaded with the action and resource. Every word contributes meaning, with no redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup tool with only two parameters and no output schema, the description is adequate. It clearly identifies the resource and scope. However, it does not describe the return format or any caveats, leaving a small gap for an otherwise simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with both parameters ('model' and 'action') fully documented. The description adds no additional parameter details beyond what the schema already provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Look up RunAPI pricing for the gemini-omni model line.' It uses a specific verb ('look up') and resource ('RunAPI pricing'), and distinguishes itself from sibling tools like create_audio and text_to_video by focusing on pricing rather than generation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for pricing lookups, but it does not explicitly state when to use this tool vs alternatives or provide exclusions. Sibling tool names suggest they serve different purposes, but no direct guidance is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

create_audioB

Run a synchronous Gemini Omni operation on RunAPI (create audio). Returns the operation result.

ParametersJSON Schema

Name	Required	Description
`name`	Yes	Audio preset display name.
`model`	No	RunAPI model slug for this model line.
`audio_id`	Yes	Voice identity used for the audio preset.
`example_dialogue`	No	Example dialogue demonstrating the voice style.
`voice_description`	No	Voice characteristics such as pitch, tone, or accent.

TDQS

B3.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses that the operation is synchronous and returns the operation result, which adds behavioral context beyond the schema. However, it does not explain side effects, permissions, or error behavior, leaving a moderate gap given the absence of annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences, front-loading the action and following with return behavior. It contains no redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description's mention of returning the operation result is useful but underspecified. It does not clarify the result structure or common use cases, leaving the description only partially complete for a 5-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% parameter description coverage, so the schema already defines each parameter. The description adds no parameter-specific meaning, making the baseline score of 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies a synchronous Gemini Omni operation, with the parenthetical 'create audio' clarifying the tool's purpose. This distinguishes it from siblings like text_to_video and create_character, though the generic verb 'run' and lack of explicit 'preset' wording slightly reduce specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. Sibling tools exist (create_character, text_to_video), but the description does not mention conditions, exclusions, or selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

create_characterC

Run a synchronous Gemini Omni operation on RunAPI (create character). Returns the operation result.

ParametersJSON Schema

Name	Required	Description
`model`	No	RunAPI model slug for this model line.
`audio_ids`	No	Audio preset IDs returned by create-audio.
`descriptions`	Yes	Character appearance, identity, style, clothing, or personality description.
`character_name`	No	Character display name.
`reference_image_url`	Yes	Public character reference image URL.

TDQS

C2.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the operation is synchronous and returns a result, but omits critical details such as side effects (is it a write/creation? are resources persisted?), authentication requirements, possible failure modes, or whether the operation is idempotent. This is insufficient for a create operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (two sentences) but not optimally front-loaded. The first sentence 'Run a synchronous Gemini Omni operation on RunAPI (create character)' is indirect; a more direct phrasing like 'Creates a character using Gemini Omni on RunAPI' would be clearer. The second sentence about the return value is useful, but the structure feels slightly awkward.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 5 parameters, no output schema, and the description does not explain what the operation result actually contains (e.g., a task ID, character data, or error details). There is also no mention of how this tool fits into a workflow (e.g., whether it depends on create_audio to provide audio_ids). Given the complexity and lack of output schema, the description is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage for all 5 parameters, so the schema already explains the meaning of fields like descriptions and reference_image_url. The description adds no additional parameter semantics beyond what the schema provides, making a baseline score of 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the tool as creating a character via a Gemini Omni operation on RunAPI, which is a specific verb+resource combination. It distinguishes from siblings like text_to_video and create_audio by focusing on character creation, though the phrase 'synchronous Gemini Omni operation' adds jargon without fully clarifying the action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as create_audio or text_to_video. No exclusions, prerequisites, or contextual triggers are mentioned, leaving the agent to infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_taskA

Fetch the current status and latest result payload for a gemini-omni task.

ParametersJSON Schema

Name	Required	Description	Default
`action`	No	Asynchronous endpoint the task was created on. Defaults to the line's only asynchronous endpoint.
`task_id`	Yes	Task id returned when the task was created.

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description carries the full burden. It discloses a read operation (fetch) but does not mention any side effects, auth requirements, or error conditions. Adequate for a simple fetch but lacks depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with the action and resource, no unnecessary words. Highly concise and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity (2 params, no output schema), the description is sufficient but could be improved by hinting at the return format or any important limitations. Not incomplete, but not rich.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the description does not add any parameter-specific details beyond what the schema already provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches current status and latest result payload for a gemini-omni task, using a specific verb and resource. It implicitly distinguishes from siblings like text_to_video which creates tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives, such as checking task status versus creating a new task. The agent must infer usage from context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

loginA

Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json.

ParametersJSON Schema

Name	Required	Description	Default
`force`	No	Re-run browser login when the current credential comes from the local config file.

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden. It discloses the interactive browser flow and the file write side effect (config.json). However, it does not mention that it may overwrite existing credentials or that it could block waiting for user input, though these are implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that front-loads the action ('Authenticate RunAPI') and provides necessary details without extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple login tool with one optional parameter and no output schema, the description covers the core purpose and side effect. It lacks an explicit statement that this is a prerequisite for other tools, but that is implied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (the only parameter 'force' has a description). The tool description adds no additional meaning about parameters beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Authenticate'), target resource ('RunAPI'), method ('browser PKCE login flow'), and side effect (saving to config.json). It is distinct from sibling tools, none of which relate to authentication.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (to authenticate RunAPI) but does not explicitly say when to run it (e.g., before other RunAPI tools) or when to use the 'force' parameter. Since there are no alternative auth tools among siblings, 'vs alternatives' is not applicable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

text_to_videoB

Create a Gemini Omni task on RunAPI (text to video). Returns a task id, status, and output URLs.

ParametersJSON Schema

Name	Required	Description
`seed`	No
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`prompt`	Yes	Video generation prompt.
`audio_ids`	No
`timeout_ms`	No
`video_list`	No
`aspect_ratio`	No	Output aspect ratio.
`callback_url`	No	Webhook URL for terminal Task delivery.
`character_ids`	No
`duration_seconds`	No
`poll_interval_ms`	No
`output_resolution`	No	Output resolution.
`reference_image_urls`	No

TDQS

B3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only mentions the return values (task id, status, output URLs) but does not explain asynchronous behavior, polling semantics, or that output URLs may not be immediately available. The default `wait=true` parameter is not mentioned, making the behavior unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no filler or redundancy. It is front-loaded with the core action. However, it is perhaps too brief for a tool of this complexity, though this is more a completeness issue than a conciseness one.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 14 parameters, no output schema, and no annotations, this description is severely under-specified. It fails to explain the task lifecycle, the wait/poll behavior, webhook options, or how to interpret the returned status. The description only scratches the surface of what the tool does.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides no parameter information whatsoever. With schema description coverage at only 43%, many parameters (seed, audio_ids, video_list, character_ids, duration_seconds, poll_interval_ms, etc.) remain undocumented in both the schema and the description. The tool description does nothing to compensate for this low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create') and the resource ('Gemini Omni task') with an explicit parenthetical 'text to video' that distinguishes it from sibling tools like create_audio and create_character. It is specific and immediately understandable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for text-to-video generation but offers no explicit guidance on when to choose this over create_audio or create_character. No alternatives or exclusion criteria are mentioned, leaving usage context implicit rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

5 tool updatesv0.2.1Aug 5, 2026
- Addedcheck_pricing
- Addedcreate_audio
- Changedcreate_character6 fields changed
  - addedInput schema / properties / audio_ids / description
```
Added value: +"Audio preset IDs returned by create-audio."
```
  - addedInput schema / properties / character_name / description
```
Added value: +"Character display name."
```
  - addedInput schema / properties / character_name / maxLength
```
Added value: +210
```
  - addedInput schema / properties / descriptions / description
```
Added value: +"Character appearance, identity, style, clothing, or personality description."
```
  - addedInput schema / properties / descriptions / maxLength
```
Added value: +20000
```
  - addedInput schema / properties / reference_image_url / description
```
Added value: +"Public character reference image URL."
```
- Addedlogin
- Changedtext_to_video5 fields changed
  - addedInput schema / properties / aspect_ratio / description
```
Added value: +"Output aspect ratio."
```
  - addedInput schema / properties / callback_url / description
```
Added value: +"Webhook URL for terminal Task delivery."
```
  - addedInput schema / properties / output_resolution / description
```
Added value: +"Output resolution."
```
  - addedInput schema / properties / prompt / description
```
Added value: +"Video generation prompt."
```
  - addedInput schema / properties / prompt / maxLength
```
Added value: +20000
```

6 tool updatesv0.2.0Jul 22, 2026

Removedcheck_pricing
Removedcreate_audio

Changedcreate_character8 fields changed

addedInput schema / properties / audio_ids

Added value: +{
+  "items": {},
+  "type": "array"
+}

addedInput schema / properties / character_name
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / descriptions / type
```
Added value: +"string"
```

removedInput schema / properties / poll_interval_ms

Removed value: -{
-  "exclusiveMinimum": 0,
-  "type": "integer"
-}

addedInput schema / properties / reference_image_url / type
```
Added value: +"string"
```

removedInput schema / properties / timeout_ms

Removed value: -{
-  "exclusiveMinimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / wait

Removed value: -{
-  "default": true,
-  "description": "Poll until the task reaches a terminal status.",
-  "type": "boolean"
-}

addedInput schema / required

Added value: +[
+  "descriptions",
+  "reference_image_url"
+]

Changedget_task3 fields changed

changedInput schema / properties / action / description

Previous value: -"Endpoint the task was created on."New value: +"Asynchronous endpoint the task was created on. Defaults to the line's only asynchronous endpoint."

changedInput schema / properties / action / enum

Previous value: -[
-  "create_audio",
-  "create_character",
-  "text_to_video"
-]New value: +[
+  "text_to_video"
+]

changedInput schema / required

Previous value: -[
-  "task_id",
-  "action"
-]New value: +[
+  "task_id"
+]

Removedlogin

Changedtext_to_video11 fields changed

addedInput schema / properties / audio_ids

Added value: +{
+  "items": {},
+  "type": "array"
+}

addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / character_ids

Added value: +{
+  "items": {},
+  "type": "array"
+}

removedInput schema / properties / duration_seconds / enum
```
Removed value: -[
-  4,
-  6,
-  8,
-  10
-]
```

changedInput schema / properties / model / enum

Previous value: -[
-  "gemini-omni-text-to-video"
-]New value: +[
+  "gemini-omni-flash-preview",
+  "gemini-omni-text-to-video"
+]

addedInput schema / properties / prompt / type
```
Added value: +"string"
```
addedInput schema / properties / reference_image_urls / items
```
Added value: +{}
```
addedInput schema / properties / reference_image_urls / type
```
Added value: +"array"
```
addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```

addedInput schema / properties / video_list

Added value: +{
+  "items": {},
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "duration_seconds"
-]New value: +[
+  "prompt"
+]

1 tool updatev0.1.6Jul 13, 2026
- Addedlogin
5 tool updatesv0.1.0Jun 24, 2026
- First observedcheck_pricing
- First observedcreate_audio
- First observedcreate_character
- First observedget_task
- First observedtext_to_video

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0

Scored 2026-08-05 02:25 across 6 tools

Disambiguation5/5

Each tool targets a distinct operation: authentication, video generation, audio generation, character creation, task retrieval, and pricing. The similar descriptions for create_audio and create_character are clarified by their names, leaving no real ambiguity.

Naming Consistency3/5

Most tools follow a verb_noun pattern (create_audio, create_character, get_task, check_pricing), but 'login' is a bare verb and 'text_to_video' is an action-object phrase without a leading verb. This mix is readable but not fully consistent.

Tool Count5/5

Six tools is a well-scoped set for a Gemini Omni integration, covering authentication, content generation, task status, and pricing. Each tool has a clear purpose and the count is appropriate for the server's domain.

Completeness4/5

The server covers core generation types (video, audio, character) and task status, but lacks operations like listing or canceling tasks. The missing lifecycle operations are minor and workable for most workflows.

Maintenance

ActivitySlowing

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

mcp-veoOAuth
io.github.AceDataCloud
MCP server for Google Veo AI video generation
Multimedia Processing Image & Video Processing Entertainment & Media
23
PixapiOAuth
io.github.Pixapi-AI
MCP server for Pixapi: check live credit pricing and balance, then generate images and video.
Image & Video Processing AI & Machine Learning
1
mcp-lumaOAuth
io.github.AceDataCloud
MCP server for Luma Dream Machine AI video generation
Multimedia Processing Image & Video Processing
2
mcp-hailuoOAuth
io.github.AceDataCloud
MCP server for Hailuo (MiniMax) AI video generation
AI & Machine Learning Image & Video Processing
21

Related MCP Servers

@runapi.ai/gpt-4o-image-mcpofficial
AI & Machine Learning Image & Video Processing
runapi-ai
A
license
A
quality
A
maintenance
MCP server for GPT-4o Image model line, enabling text-to-image task creation, status polling, and pricing checks via RunAPI.
Updated a month ago (2026-07-31 09:32 UTC)
4
110
Apache 2.0
imagen-4-mcp
AI & Machine Learning Image & Video Processing
runapi-ai
A
license
A
quality
A
maintenance
RunAPI MCP server for the Imagen 4 model line. Create tasks, poll their status, and check pricing through a single RunAPI API key.
Updated a month ago (2026-07-31 09:34 UTC)
5
65
Apache 2.0
infinitetalk-mcp
AI & Machine Learning Multimedia Processing
runapi-ai
A
license
A
quality
A
maintenance
MCP server for the InfiniteTalk model line, enabling audio-to-video task creation, status polling, and pricing checks via a RunAPI API key.
Updated a month ago (2026-07-31 09:35 UTC)
4
64
Apache 2.0
@runapi.ai/runway-aleph-mcpofficial
AI & Machine Learning Multimedia Processing
runapi-ai
A
license
A
quality
A
maintenance
MCP server for the Runway Aleph model line. Enables creating edit video tasks, polling status, and checking pricing through a single RunAPI API key.
Updated a month ago (2026-07-31 09:39 UTC)
4
66
Apache 2.0

Why This Package?

Install

Tools

Models

Agent Prompts

Create a task

Submit without waiting

Check pricing before creating

Configuration

Links

License

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

@runapi.ai/gpt-4o-image-mcpofficial

@runapi.ai/runway-aleph-mcpofficial