gemini-omni-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SURFACE | No | The Google surface to target: gemini, flow, or youtube (default: gemini) | gemini |
| TIMEOUT | No | Timeout in milliseconds for browser operations (default: 30000) | 30000 |
| HEADLESS | No | Run browser in headless mode (true/false, default: false) | false |
| OUTPUT_DIR | No | Directory for generated video files (default: output) | output |
| PROFILE_DIR | No | Directory for persistent Chrome profile (default: .auth-profile) | .auth-profile |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| omni_statusA | Check whether the Gemini session is signed in and whether a generation is in progress. |
| omni_generate_videoA | Generate a video with Gemini Omni. IMPORTANT: do NOT pass a raw one-liner — first run the creation interview in GUIDE.md (subject, action, setting, style, lighting, camera, aspect ratio, consistency, mood) and pass either a fully-formed |
| omni_edit_videoA | Edit an existing video with Gemini Omni (it keeps characters, physics and scene continuity). Describe ONE change in plain language. Restate what stays the same, then the change. See GUIDE.md §1. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct and clearly defined purpose: editing videos, generating videos, and checking session status. No overlap in functionality.
All tool names follow a consistent pattern with the 'omni_' prefix and verb_noun construction (edit_video, generate_video, status).
Three tools is appropriate for a focused video generation and editing server, covering the essential operations without unnecessary extras.
The tool surface covers generation, editing, and status checking. Missing operations like listing or deleting videos, but these are not core to the stated purpose.