google-flow-mcp
Provides automation for Google Flow (flow.google.com), enabling creation of consistent characters, generation of Veo 3.1 and Omni videos plus Nano Banana images, scene assembly and MP4 export, Flow agent chat, and management of project instructions/defaults with credit guardrails.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Google Flow MCP Server: Veo 3.1 and Omni AI Video Generation for Claude, Cursor and AI Agents
google-flow-mcp is an open source MCP server for Google Flow (flow.google.com), Google's AI filmmaking studio. It lets Claude, Claude Code, Cursor or any Model Context Protocol client create consistent AI characters, generate Veo 3.1 and Omni videos with them, assemble scenes, export finished MP4s, chat with the Flow agent and set agent instructions. In short, it automates everything you normally click through in the Google Flow UI.
Use it to automate AI video production: short-form reels, AI influencer content, storyboards, ads and multi-shot stories with the same character in every clip.
Unofficial. Not affiliated with or endorsed by Google. It works with Flow's private web app, which can change at any time. Use your own account, follow Google's terms, and keep an eye on your credits.
Table of contents
Related MCP server: io.github.ethanhamilthon/yenflow
Features
Consistent characters. Create reusable Flow characters with a generated portrait, a voice (30 built-in voices) and personality notes, then feature them in any clip so they look the same every time.
AI video generation. Generate clips with Omni 1.1 Flash (4 to 10 s, 360p or 720p) or Veo 3.1 Lite, Fast and Quality, from text or with characters and reference images as ingredients.
Video editing. Change an existing clip with a plain instruction ("make it night, add rain").
Image generation. Nano Banana images for references, storyboards and start frames.
Scenes and export. Build a scene timeline in Flow, then export the whole scene to a single MP4 (ffmpeg normalises size, frame rate and audio).
Flow agent. Talk to Flow's built-in creative agent, attach characters, and approve its generations within a credit budget.
Agent instructions and model defaults. Manage the project's Agent instructions, default image and video models, aspect ratios, counts and the "ask before spending credits" setting.
Credit guardrails. Every generating call reads Flow's own price quote first, refuses above your cap and supports
dry_run.Model catalog. Lists every model with its mode, duration, resolution and credit price.
How it works
The server drives a Chrome tab that you are signed in to, using Playwright:
Reads and edits (projects, characters, scenes, clips, instructions, defaults, job status, media links) use Flow's own web API from inside that tab. This is fast and reliable.
Generation (portraits, images, videos, edits, agent chat) goes through Flow's real UI. The server attaches ingredients, picks settings, types the prompt and presses Generate, the same way you would. Flow protects generation with reCAPTCHA Enterprise and refuses requests that don't come from its UI, so this project deliberately does not try to bypass that. If Flow declines a request, you get Flow's error back and nothing is retried.
Your password and cookies never leave your browser. The server stores nothing except an optional local Chrome profile.
Quick start
Requirements: Node.js 20+, Google Chrome, a Google account with Flow access, and ffmpeg on your PATH (only needed for scene export).
git clone https://github.com/RohaanA/google-flow-mcp.git
cd google-flow-mcp
npm install
npm run build
npm testPick one way to give the server a signed-in browser.
Option A: your own Chrome (recommended). Start Chrome with remote debugging, sign in at flow.google.com and keep the window open.
# macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 --user-data-dir="$HOME/.flow-chrome"
# Windows (PowerShell)
& "C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir="$env:USERPROFILE\.flow-chrome"
# Linux
google-chrome --remote-debugging-port=9222 --user-data-dir="$HOME/.flow-chrome"Then set FLOW_CDP_URL=http://127.0.0.1:9222.
Option B: a dedicated profile. Run npm run login, sign in to Flow in the window that opens, then close it. The
server will launch Chrome with that profile (~/.google-flow-mcp/profile).
Connect to Claude Desktop, Claude Code or Cursor
Add the server to your MCP client config (for example claude_desktop_config.json, .mcp.json or Cursor's
mcp.json):
{
"mcpServers": {
"google-flow": {
"command": "node",
"args": ["/absolute/path/to/google-flow-mcp/dist/index.js"],
"env": {
"FLOW_CDP_URL": "http://127.0.0.1:9222",
"FLOW_MAX_CREDITS_PER_CALL": "20",
"FLOW_OUTPUT_DIR": "/absolute/path/to/FlowExports"
}
}
}
}With Claude Code you can also run:
claude mcp add google-flow -e FLOW_CDP_URL=http://127.0.0.1:9222 -- node /absolute/path/to/google-flow-mcp/dist/index.jsEnvironment variable | Default | Purpose |
| unset | Attach to your running Chrome instead of launching one |
|
| Chrome profile for option B |
|
| Which browser to launch |
|
| Launch headless (read-only use) |
|
| Default credit cap for each generating call |
|
| Where downloads and scene exports go |
Tools reference
Area | Tool | What it does |
Account |
| Checks the browser session and returns your credit balance |
| Omni and Veo models with mode, duration, resolution and credit price | |
| Voices you can give a character | |
Projects |
| List or create Flow projects |
| Characters, generations, scenes with clips, agent instructions and defaults | |
Characters |
| Name, generated portrait, voice and personality |
| Rename, change voice or personality | |
| Change a character's look with an instruction | |
Images |
| Nano Banana images, optionally with characters or reference images |
Video |
| Text-to-video or character/reference video; |
| Edit an existing clip with an instruction | |
| Poll or wait for jobs; returns signed video URLs | |
| Fetch or download images and videos | |
Scenes |
| Build an ordered scene timeline |
| Join a scene's clips into one MP4 | |
Agent |
| Chat with Flow's agent and approve or reject its credit requests |
Settings |
| Add, replace or remove the project's Agent instructions |
| Default image and video models, aspect, count and credit approval policy |
Example prompts
Paste these into Claude (or any MCP client) once the server is connected:
"Create a Flow project called Street Food Diaries and a character Maya: late 20s travel vlogger, curly dark hair, olive jacket, voice aoede, upbeat and curious."
"Make three 4 second 360p vertical clips of Maya at a night market, wait for them, put them in a new scene and export it."
"What would a 720p 8 second Omni clip of Maya cost? Do a dry run."
"Add an agent instruction: always shoot handheld vlog style in 9:16 with natural light."
"Ask the Flow agent to storyboard a 30 second reel with Maya, and approve anything under 20 credits."
Credits and safety
Generating spends your Flow credits. Every generating tool reads Flow's own quote ("Generating will use N credits") and refuses when it is above
max_credits(default 20, orFLOW_MAX_CREDITS_PER_CALL).Use
dry_run: trueto see the price without generating. 360p and 4 s Omni clips are the cheapest drafts.flow_agent_chatnever approves the agent's spending unless you setmax_credits.Generation runs one job at a time in a single tab. Avoid using that tab yourself while a job is running.
Status and limitations
Tested against a live account:
reading projects, characters, scenes, media and job status
creating and updating characters
creating scenes and adding clips
agent instructions, defaults and credit approval policy
character-reference video generation through the UI; the request Flow's UI sent matches this project's request builder field for field (see
test/protocol.test.mjs)
Implemented but less tested:
portrait creation, image generation, video edit and agent chat through the UI
Veo menus, which may offer different durations than Omni
Not supported yet:
start/end-frame video
extend
upsample
media upload
Pull requests welcome.
Because Flow's web app is private and changes often, selectors or payloads can break after a Google update. The protocol notes in PROTOCOL.md and the tests make fixes quick.
FAQ
Is there an official Google Flow API? Not for Flow itself. Google offers Veo through the Gemini API and Vertex AI, which is the stable choice for pure video generation. This project is for people who want Flow's features (characters, scenes, the Flow agent, Omni models) from an AI agent.
Does this work with Claude Code, Cursor, Windsurf or other MCP clients? Yes. It is a standard stdio MCP server, so any Model Context Protocol client can use it.
Can I generate Veo 3.1 videos with consistent characters?
Yes. Create a character once, then pass its id (or name) in character_ids. The clip uses Flow's
reference-to-video models so the character stays consistent.
Does it bypass Flow's limits or captcha? No. Generation goes through Flow's normal UI and uses your own account, credits and limits. If Flow refuses a request, the tool reports it.
Is my Google password or cookie stored? No. The server controls a browser you signed in to yourself and never reads or saves your credentials.
Why does it need Chrome? Flow only allows generation from its own web app, so the server works through a real, signed-in browser session.
Contributing
Issues and pull requests are welcome, especially:
start/end-frame video support
Veo-specific settings
uploads
selector fixes after Flow updates
Run npm test before opening a PR, and never commit real account ids, tokens or signed URLs in fixtures.
Keywords
Google Flow API, Google Flow MCP, Veo 3.1 MCP server, Veo 3 automation, Omni video, Nano Banana, AI video generation, AI filmmaking, consistent AI characters, AI influencer video, text to video, reference to video, Claude MCP, Claude Code, Cursor MCP, Model Context Protocol, Playwright automation, scene export, ffmpeg.
License
MIT. Google, Google Flow, Veo and Nano Banana are trademarks of Google LLC. This project is independent and unofficial.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Connect Claude or any MCP client to Wireflow, the AI canvas for image, video and audio workflows. List, build, inspect and run your workflows and published apps, browse templates, check models, prices and credits, edit a video node's timeline, and plan or schedule social posts. Drafts and edits cost no credits; run tools spend the user's credits.
Build, run, schedule, and publish AI video pipelines to YouTube and TikTok from any MCP client.
Google Flow's agent: chat that plans and makes images and videos, approvals, your own media
Generate images and videos with Seedance, Veo, Wan, Grok, GPT-Image and Nano Banana via one MCP.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables Claude to drive Google Flow end-to-end: batch video generation on Veo 3 / Omni 1.1, scene chaining, keyframe transitions, video-to-video edits, and automatic downloads, all through a local bridge with the OmniFlow Chrome extension.5142 npmMIT
- AlicenseCqualityBmaintenanceEnables AI agents to orchestrate Google Flow video and image generation, including multi-scene planning, silent background generation, credit tracking, and video stitching via MCP.25MIT
- AlicenseCqualityCmaintenanceEnables Claude, Cursor, or any MCP client to create consistent AI characters, generate Veo 3.1 and Omni videos, edit clips, build scenes, export MP4s, and chat with Google Flow's creative agent. Automates AI video production workflows such as reels, storyboards, and multi-shot stories through natural language, with credit guardrails and dry-run pricing.2316MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents from an MCP client to control Google Flow through a signed-in Chrome session, generating videos and images with Veo, Nano Banana, and Omni while managing projects, assets, scenes, characters, and shot lists with spending-approval guards and a sandboxed file vault.5MIT