Google Flow MCP
Generate and download Google Flow videos and images directly from AI agents—using your existing Google subscription, with no generation API key.
에이전트 강화
게시자가 제공하는 설치 방식입니다. PlugMCP 엔드포인트가 아닙니다.
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행게시자 제공
Generate and download Google Flow videos and images directly from AI agents—using your existing Google subscription, with no generation API key.
Generate and download Google Flow videos and images from Codex, Antigravity, and any MCP agent. Live Omni, Veo, and Nano Banana capabilities, easy Chromium login, multi-account sessions, upscaling, and validated local files—no generation API key.
Works with OpenAI Codex, Google Antigravity, and other local stdio MCP clients.
Google Flow MCP is a local Model Context Protocol server that lets an AI agent operate Google Flow through a user-owned Chromium session. It can discover the exact options available to each account, generate media with Flow subscription credits, wait for long-running jobs, use the upscale choices Flow actually offers, and save validated files directly into a project.
It does not require a Google generation API key. Credits are consumed through the Flow website just as they are when the user operates Flow manually.
Installing with an agent? Tell it to read AGENTS.md and follow INSTALL.md. The supported Antigravity command is
npm run setup:antigravity. Installer agents must not modify source, install Playwright Chromium, generate tool schemas, or use an Antigravity scratch directory.
flow_inspect_account returns a live, normalized capability contract instead of relying on hardcoded assumptions:
Example from a real Spanish-language Flow account:
{
"models": {
"image": [
{ "id": "nano-banana-pro", "label": "Nano Banana Pro", "selected": false },
{ "id": "nano-banana-2", "label": "Nano Banana 2", "selected": true },
{ "id": "nano-banana-2-lite", "label": "Nano Banana 2 Lite", "selected": false }
],
"video": [
{ "id": "omni-flash", "label": "Omni Flash", "selected": true },
{ "id": "veo-3-1-lite", "label": "Veo 3.1 - Lite", "selected": false },
{ "id": "veo-3-1-fast", "label": "Veo 3.1 - Fast", "selected": false },
{ "id": "veo-3-1-quality", "label": "Veo 3.1 - Quality", "selected": false }
]
},
"aspectRatiosByMedia": {
"image": ["16:9", "4:3", "1:1", "3:4", "9:16"],
"video": ["16:9", "9:16"]
},
"outputCountsByMedia": {
"image": [1, 2, 3, 4],
"video": [1, 2, 3, 4]
},
"visibleDurations": [],
"availableUpscales": ["1080p"],
"unavailableUpscales": ["4k"]
}
If Flow does not offer a requested model, ratio, duration, output count, or upscale, the MCP fails explicitly. It never silently substitutes a different paid option.
The bundled Flow Login Bridge extension reuses Google accounts already signed into the user's normal Chromium profile. Connection is deliberately split into two MCP calls so the agent can explain each user action instead of disappearing into a long-running tool:
flow_begin_account_connection returns immediately and instructs the agent to stop and tell the user what to click.flow_complete_account_connection opens Google's existing-account chooser; the user clicks the desired account.No email entry, password entry, 2FA entry, cookie JSON, Chromium restart, or remote-debugging launch is required for the normal login path.
1080p.flow.json reproducibility manifestffprobe is installedGeneration and upscale tools require confirmCreditSpend: true. The agent should set it only after the user explicitly asks for a credit-consuming operation. Read-only inspection, status, and account-list tools do not spend credits.
Flow MCP also owns Flow's separate in-browser confirmation preference. Before submitting a generation, it opens the isolated managed profile's Agent settings, selects the language-independent AUTO_APPROVE value (shown as Never / Nunca), saves it, reopens the settings, and verifies that it persisted. If Flow still displays an approval card, the MCP selects the final persistent approval action—Approve and don't ask again—instead of leaving the agent waiting or choosing the one-time approval.
This does not bypass the MCP credit guard: a generation or upscale still runs only when the user requested it and the tool call includes confirmCreditSpend: true.
The MCP publishes a server-level execution contract as part of the MCP initialization handshake and repeats the critical rules in every relevant tool description and response:
flow_generate_video or flow_generate_imageflow_access_unavailable errorThis prevents an agent from scrolling around Flow's marketing site when the selected Google account is signed in but does not expose the generation workspace.
ffprobe on PATH for richer media validationgit clone https://github.com/retrolyze52/google-flow-mcp.git
cd google-flow-mcp
npm ci
npm run check
Playwright controls the locally installed Chromium/Chrome executable; it does not require a separate bundled browser download. Do not run npx playwright install chromium. Set FLOW_MCP_BROWSER_EXECUTABLE to an absolute browser path only if auto-detection cannot find a normal system browser. See the complete installation guide.
The reviewed extension source is included in extension/. It reads Google cookies only after the user clicks Connect Flow and sends them only to the MCP bridge bound to 127.0.0.1. It never reads passwords or 2FA codes.
On Windows with Chromium:
npm run install-extension
The helper copies the extension path and opens chrome://extensions/. Then:
extension directory.For Chrome or another desktop platform, open chrome://extensions/ manually and follow the same three steps. No browser restart is needed.
Ask the agent:
Connect my Google Flow account as
personal.
The correct interaction is:
flow_begin_account_connection, shows you its instructions, and stops.flow_complete_account_connection.That is the complete normal login flow. Completion is detected automatically and the temporary Flow window closes.
To connect additional accounts, repeat the process with IDs such as studio or backup. Each account receives an isolated persistent browser profile. Operations for one account are serialized; separate accounts can progress independently.
CLI equivalents are also available:
npm run account -- connect personal "Personal Google Pro"
npm run account -- connect studio "Studio account"
npm run account -- list
If a browser was deliberately started with a localhost remote-debugging port, the MCP can attach without copying cookies:
npm run account -- connect personal "Main Chromium" --cdp http://127.0.0.1:9222
Only localhost CDP endpoints are accepted, and attached browsers are never closed by the MCP. The extension flow is recommended for normal setup.
Run npm run build first. Replace the paths below with the absolute location of dist/index.js.
Add this to ~/.codex/config.toml:
[mcp_servers.google_flow]
command = "node"
args = ["C:\\absolute\\path\\to\\google-flow-mcp\\dist\\index.js"]
enabled = true
startup_timeout_sec = 30
tool_timeout_sec = 1200
[mcp_servers.google_flow.env]
FLOW_MCP_HEADLESS = "0"
Open a new Codex task after changing MCP configuration. This does not restart Chromium or require another Google login.
Antigravity 2.0, Antigravity IDE, and Antigravity CLI support local stdio MCP servers. Clone into a stable directory—not Antigravity's disposable scratch directory—then run the supported installer:
git clone https://github.com/retrolyze52/google-flow-mcp.git "$env:LOCALAPPDATA\google-flow-mcp"
Set-Location "$env:LOCALAPPDATA\google-flow-mcp"
npm run setup:antigravity
The installer enforces a clean source tree, runs all checks, detects a normal browser, preserves unrelated MCP servers, backs up the existing config, and writes the official ~/.gemini/config/mcp_config.json stdio structure with absolute command, args, and cwd paths. Then open Settings → Customizations → Installed MCP Servers and click Refresh. Antigravity discovers schemas automatically; do not generate them. This refresh does not restart Chromium or lose connected Flow accounts. See INSTALL.md and Google's official Antigravity MCP documentation.
{
"mcpServers": {
"google-flow": {
"command": "node",
"args": ["/absolute/path/to/google-flow-mcp/dist/index.js"]
}
}
}
Once the account is connected, users can speak normally:
Inspect my Flow account and tell me exactly which image models, video models, ratios, durations, output counts, and upscales are available.
Use Omni Flash to create one 16:9 video of a translucent glass jellyfish floating through a rainy neon city. Download it into
public/generated/flow. Do not upscale it.
Generate a vertical image with Nano Banana 2 Lite using the attached reference image and save it for my Remotion project.
Upscale the last video to the highest resolution my account actually offers. Do not choose an unavailable or upgrade-only option.
The expected agent workflow is:
flow_help when the user asks what the MCP can doflow_list_accountsflow_begin_account_connection, user instructions, and a hard stop when connection is neededflow_complete_account_connection only after the user confirms the extension clickflow_inspect_account immediately before generationflow_generate_video or flow_generate_image after explicit authorizationflow_job_status for long-running workflow_upscale_video when requestedflow_download_job for a ready asset that has not yet been downloadedflow_list_accounts returns connectionStatus, connectedAccountIds, defaultAccountId, and an explicit next action. After a successful connection, that account automatically becomes the verified default. Generation and inspection calls may omit accountId to use it; provide an ID only when the user deliberately selects another connected account.
Flow may insert a newly generated asset anywhere in the project gallery; DOM order is not a creation timestamp. Google Flow MCP snapshots the existing asset identities before submitting a prompt, records only the identities that appear for that job, and uses those same identities for later upscale and download actions. It never substitutes “the last video” or “the latest visible image.” If the tracked identity disappears or becomes ambiguous after a Flow UI/session change, the operation stops with generated_asset_not_found instead of downloading a different asset.
Flow often keeps completed gallery videos hidden or off-screen without loading HTML video metadata. Readiness is therefore verified against the exact generated media URL, and original downloads use that same authenticated URL directly. Generation tools wait at most 20 seconds after submission; if Flow is still queued, they return processing with a persistent job ID. The agent must poll that same ID—never submit the prompt again.
Example video tool input:
{
"prompt": "A cinematic tracking shot through a rainy miniature neon city, shallow depth of field, reflections on wet streets, no text",
"model": "omni-flash",
"aspectRatio": "16:9",
"outputs": 1,
"referenceFiles": [],
"upscale": "none",
"outputDirectory": "C:\\projects\\my-remotion-video\\public\\generated\\flow",
"download": true,
"timeoutSeconds": 600,
"confirmCreditSpend": true
}
For Remotion, files saved under public/generated/flow can be loaded with staticFile("generated/flow/<file>.mp4").
Upscaling is a real Flow asset action, not local interpolation:
2x or 1080p fail if that exact option is unavailable.highest_available ranks only options Flow currently offers.The MCP never invents 4x, silently downgrades a request, or substitutes an unrelated local upscaler.
Every tool includes MCP-visible parameter descriptions so the agent knows how to use the live IDs returned by flow_inspect_account.
That behavior is not a Flow MCP generation. Check the agent's tool trace: it must contain flow_generate_video or flow_generate_image and the response must contain a job ID. Version 0.2.0 adds a deterministic installer and non-blocking account onboarding in addition to the browser-fallback guard. Refresh or restart the MCP client after upgrading so it reloads the current server instructions and tool schemas.
If the MCP itself returns flow_access_unavailable, the selected Google identity is signed in but did not reach the Flow workspace. Restart the begin/complete connection workflow and select another account that has Flow access. Do not browse or scroll the landing page.
Runtime state stays outside the repository by default:
%LOCALAPPDATA%\flow-mcp~/Library/Application Support/flow-mcp$XDG_DATA_HOME/flow-mcp or ~/.local/share/flow-mcpflow-mcp/
accounts.json
profiles/<account-id>/
jobs/<job-id>.json
diagnostics/*.png
Override the location with FLOW_MCP_DATA_DIR. Never commit that directory. If Flow changes its UI, errors include a diagnostic screenshot where possible; selectors intentionally prefer semantic roles and stable Material Symbols over translated text or hashed CSS classes.
127.0.0.1 on a small fixed port range.The extension necessarily has powerful access to Google cookies. Install only a reviewed copy from this repository. See SECURITY.md for the threat model and responsible disclosure process.
Alpha. The core workflow has been live-tested with an existing Chromium account, a Spanish Flow interface, live model/ratio/upscale discovery, one real Omni Flash generation, persistent polling, browser download capture, and FFprobe validation.
Google Flow does not provide a stable public browser-automation contract. UI changes can break selectors even with structural discovery and defensive failure behavior. Live Google-account tests are intentionally excluded from CI because they would require private sessions and spend credits.
Current priorities:
npm ci
npm run typecheck
npm test
npm run check
npm pack --dry-run
The included CI workflow targets Windows and Linux with Node.js 20 and 24. Contributions are welcome; see CONTRIBUTING.md.
MIT. This is an independent, clean-room project. It is not affiliated with, endorsed by, or supported by Google. Google Flow, Gemini, Veo, Nano Banana, Omni, Chromium, Codex, Antigravity, and Remotion are trademarks or products of their respective owners.
Use this project in accordance with Google's terms and all applicable policies.
Generate and download Google Flow videos and images from Codex, Antigravity, and any MCP agent. Live Omni, Veo, and Nano Banana capabilities, easy Chromium login, multi-account sessions, upscaling, an
개요
Generate and download Google Flow videos and images from Codex, Antigravity, and any MCP agent. Live Omni, Veo, and Nano Banana capabilities, easy Chromium login, multi-account sessions, upscaling, and validated local files—no generation API key.
도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
Google Flow은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-10-28. Generate and download Google Flow videos and images from Codex, Antigravity, and any MCP agent. Live Omni, Veo, and Nano Banana capabilities, easy Chromium login, multi-account sessions, upscaling, and validated local files—no generation API key.