gemini-omni-mcp

An MCP server that lets Claude (or any MCP client) control Google Gemini Omni — Google's new "any-to-any" video-generation model (announced at Google I/O 2026).

Why a browser bridge? As of June 2026, Gemini Omni has no public developer API. Google said the Vertex AI rollout is "coming in the coming weeks." Until then, Omni only exists inside the Gemini app, Google Flow, and YouTube. This server bridges that gap by driving a logged-in Chrome session — and is built so it can swap to the official API in one place the moment it ships.

How it works

Claude  ──MCP──►  gemini-omni-mcp  ──Playwright──►  Chrome (your Google login)  ──►  Gemini Omni

• Your Google login lives in a persistent Chrome profile (.auth-profile/). You sign in once, yourself — the code never sees, types, or stores your password.

• Tools are exposed over MCP so Claude can call them directly.

Related MCP server: gemini-skill

Status

🚧 Phase 1 — scaffold (this commit). MCP server, browser session manager, and tool definitions are in place. The UI automation selectors are placeholders, to be mapped against the live Gemini Omni interface in Phase 2.

Setup

npm install
npx playwright install chromium
npm run build
npm run auth      # opens Chrome — log in to Google once

Use as an MCP server in Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "gemini-omni": {
      "command": "node",
      "args": ["C:/Users/tamir/Desktop/gemini-omni-mcp/dist/index.js"]
    }
  }
}

Creating the perfect video

Don't fire a one-line prompt. The project ships a creation interview — subject, action, setting, style, lighting, camera, aspect ratio, consistency, mood — plus support for editing an existing video. The tools accept a structured brief, not just a string, to nudge the caller into gathering those details first. See GUIDE.md for the full flow and prompt template.

Tools

Configuration

See .env.example. Copy it to .env to override defaults (profile dir, output dir, surface, headless, timeout).

License

MIT