Schema | Gemini Omni MCP

Gemini Omni MCP

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`OUTPUT_DIR`	No	Directory for output videos	~/gemini_omni_videos
`GEMINI_API_KEY`	Yes	Your Google Gemini API key
`MAX_BATCH_SIZE`	No	Maximum batch size for batch generation
`REQUEST_TIMEOUT`	No	Timeout for API requests
`DEFAULT_DELIVERY`	No	Default delivery method (uri or inline)
`FILE_POLL_TIMEOUT`	No	Poll timeout for file operations
`FILE_POLL_INTERVAL`	No	Poll interval for file operations
`DEFAULT_ASPECT_RATIO`	No	Default aspect ratio for videos
`DEFAULT_DURATION_SECONDS`	No	Default duration in seconds

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }
`logging`	{}
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`extensions`	{ "io.modelcontextprotocol/ui": {} }
`experimental`	{}

Tools

Functions exposed to the LLM to take actions

Name	Description
generate_videoA	Generate or edit MP4 videos with Gemini Omni Flash (gemini-omni-1.1-flash). Capabilities: text_to_video: prompt-only video with generated audio. image_to_video: one reference image plus motion and camera direction. reference_to_video: multiple reference images for subjects, style, or props. edit: use previous_interaction_id or input_video_path to edit existing video. extend: continue a video from previous_interaction_id or an uploaded MP4, appending a 3-10 second seamless continuation (repeat up to 40s total). Parameters: prompt: Describe the scene, motion, camera movement, lighting, mood, and audio. task: text_to_video, image_to_video, reference_to_video, edit, or extend. If omitted, inferred. Prefer omitting it for edit and extend: the API rejects an explicit task together with previous_interaction_id, so multi-turn edit/extend are prompt-based (e.g. "Extend this video"). aspect_ratio: 16:9 landscape or 9:16 portrait. resolution: 360p, 720p (default), 1080p, or 4k. Values above 720p are upscaled. reference_image_paths: Up to 6 local images. Use , , or tags in the prompt for control. input_video_path: Local MP4 (10s or less) to upload and edit or extend through the Files API. delivery: uri is recommended for generated MP4 files; inline is supported for smaller payloads. previous_interaction_id: Continue editing or extending a prior generated video. enhance_prompt: Optional, default false. For edits, simple prompts usually work better. Prompt tips: By default Omni generates a few different shots with cuts, crafting a narrative from the prompt. Ask for "single continuous shot, no scene cuts" when you want one unbroken scene. Stage your own cuts with timing language: "Every 2s cut to a new frame", rapid-fire sequences, or timecode lines like [0-3s], [3-6s], [6-10s]. Include explicit audio direction such as "gentle ambient room tone, no dialogue". For edits, keep prompts simple and say "Keep everything else the same". When extending, 0s in timecodes refers to the start of the extended part, and you can cut to a new scene with the same characters ("Show the same characters in the next scene"). For first/last-frame interpolation, pass two images and use tags. Limitations: Output is MP4, 3-10s clips at 24fps (360p/720p/1080p/4k), SynthID-watermarked. System instructions, temperature, top_p, stop sequences, negative_prompt, voice edits, YouTube sources, and multi-video reasoning are unsupported. Uploaded-video editing and extension are unavailable in some regions. Returns JSON including video.path, interaction_id, task, aspect_ratio, resolution, delivery, size, and URI metadata. After success, open video.path with the native OS video viewer.
batch_generateA	Generate multiple Gemini Omni Flash videos in conservative parallel batches. Use for storyboards, aspect-ratio or resolution comparisons, or reference-guided variations. Batch size defaults to configuration and is capped at 4 because video jobs are long. The JSON response includes per-prompt video.path, interaction_id, metadata, and errors.

Name

Description

generate_videoA

Generate or edit MP4 videos with Gemini Omni Flash (gemini-omni-1.1-flash).

Capabilities:

text_to_video: prompt-only video with generated audio.
image_to_video: one reference image plus motion and camera direction.
reference_to_video: multiple reference images for subjects, style, or props.
edit: use previous_interaction_id or input_video_path to edit existing video.
extend: continue a video from previous_interaction_id or an uploaded MP4, appending a 3-10 second seamless continuation (repeat up to 40s total).

Parameters:

prompt: Describe the scene, motion, camera movement, lighting, mood, and audio.
task: text_to_video, image_to_video, reference_to_video, edit, or extend. If omitted, inferred. Prefer omitting it for edit and extend: the API rejects an explicit task together with previous_interaction_id, so multi-turn edit/extend are prompt-based (e.g. "Extend this video").
aspect_ratio: 16:9 landscape or 9:16 portrait.
resolution: 360p, 720p (default), 1080p, or 4k. Values above 720p are upscaled.
reference_image_paths: Up to 6 local images. Use , , or tags in the prompt for control.
input_video_path: Local MP4 (10s or less) to upload and edit or extend through the Files API.
delivery: uri is recommended for generated MP4 files; inline is supported for smaller payloads.
previous_interaction_id: Continue editing or extending a prior generated video.
enhance_prompt: Optional, default false. For edits, simple prompts usually work better.

Prompt tips:

By default Omni generates a few different shots with cuts, crafting a narrative from the prompt. Ask for "single continuous shot, no scene cuts" when you want one unbroken scene.
Stage your own cuts with timing language: "Every 2s cut to a new frame", rapid-fire sequences, or timecode lines like [0-3s], [3-6s], [6-10s].
Include explicit audio direction such as "gentle ambient room tone, no dialogue".
For edits, keep prompts simple and say "Keep everything else the same".
When extending, 0s in timecodes refers to the start of the extended part, and you can cut to a new scene with the same characters ("Show the same characters in the next scene").
For first/last-frame interpolation, pass two images and use tags.

Limitations:

Output is MP4, 3-10s clips at 24fps (360p/720p/1080p/4k), SynthID-watermarked.
System instructions, temperature, top_p, stop sequences, negative_prompt, voice edits, YouTube sources, and multi-video reasoning are unsupported.
Uploaded-video editing and extension are unavailable in some regions.

Returns JSON including video.path, interaction_id, task, aspect_ratio, resolution, delivery, size, and URI metadata. After success, open video.path with the native OS video viewer.

batch_generateA

Generate multiple Gemini Omni Flash videos in conservative parallel batches.

Use for storyboards, aspect-ratio or resolution comparisons, or reference-guided variations. Batch size defaults to configuration and is capped at 4 because video jobs are long. The JSON response includes per-prompt video.path, interaction_id, metadata, and errors.

Prompts

Interactive templates invoked by user choice

Name	Description
`continuous_cinematic_scene`	Single-shot cinematic scene prompt for generate_video.
`image_to_video_motion`	Reference-image motion prompt for generate_video.
`timed_sequence`	Timed 10-second sequence prompt.
`edit_instruction`	Simple video-edit prompt for previous_interaction_id workflows.
`batch_storyboard`	Storyboard prompt list for batch_generate.

Resources

Contextual data attached and managed by the client

Name	Description
No resources

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored 2026-09-11 12:45 across 2 tools

Disambiguation4/5

generate_video and batch_generate have clearly separable purposes (single vs. parallel-batch generation), so an agent can pick between them. The main ambiguity is internal to generate_video, which bundles five task modes behind one tool name, but that is parameter-level rather than a collision between two tools.

Naming Consistency4/5

Both names use snake_case and are immediately readable. The only minor deviation is the ordering convention: generate_video is verb_noun while batch_generate is qualifier_verb, but this is a trivial and understandable variation.

Tool Count3/5

Two tools is thin for a video generation server; the entire surface collapses into one overloaded mega-tool plus a batch wrapper. It is defensible because the mega-tool is explicitly scoped, but the count sits in the borderline range flagged by the rubric.

Completeness4/5

The core lifecycle is covered: text/image/reference-to-video generation, editing, extension, and batching, with interaction_id chaining for multi-turn work. There is no dedicated job-status or retrieval/download tool, which is a minor gap for long-running batch jobs.

Maintenance

ActivityMaintained

ResponsivenessNo issues

Resources

Need Help?

Related Servers