Google Flow MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FFMPEG_PATH | No | Explicit FFmpeg binary for the finishing engines. | PATH |
| PYTHON_PATH | No | Explicit Python binary for the finishing engines. | PATH |
| FLOW_HTTP_PORT | No | Local API + /connect page + /mcp endpoint port. | 4318 |
| FLOW_TRANSPORT | No | Transport mode. `both` = stdio MCP + HTTP API in one process. | stdio |
| FLOW_HTTP_TOKEN | No | Bearer token for the HTTP surface; requires at least 24 characters. | |
| FLOW_WATERMARK_METHOD | No | Finishing method. `unblend` / `inpaint` / `ffmpeg`. | auto |
| FLOW_WATERMARK_REMOVAL | No | Finishing stage toggle. | true |
| FLOW_DEFAULT_VIDEO_MODEL | No | Default video model. `veo-3.1-fast` / `veo-3.1-quality` also available. | gemini-omni-flash |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| trigger_flowB | Trigger a legacy bridge workflow record by name with optional input parameters. This is not a Google Flow/Veo generation. |
| list_flowsB | List legacy bridge workflow records. These are not Google Flow/Veo projects. |
| get_flow_statusB | Get the status of a legacy bridge workflow record. |
| create_flowB | Create a legacy bridge workflow record with defined steps; this does not create a Google Flow UI workflow. |
| delete_flowB | Mark a legacy bridge workflow record deleted by ID. |
| generate_videoA | Create a durable Google Flow video job. The instruction is interpreted as a director brief, compiled into a Flow prompt, and processed asynchronously by default. |
| generate_imageA | Create a durable Google Flow IMAGE job: still renders in any Flow aspect ratio (16:9, 4:3, 1:1, 3:4, 9:16) with 1-4 variations, then watermark removal and local delivery. The prompt is passed to Flow verbatim as the visual instruction. |
| flow_capabilitiesA | Read-only capability sheet for Google Flow as driven by this server: modes, aspect ratios, durations, models, output counts, the watermark-removal engine, and where finished files are delivered. Consult it whenever a caller asks what Flow can do or which sizes/ratios are available. |
| get_video_statusC | Compatibility alias for get_video_job. Checks durable local jobs first, then a legacy authenticated bridge request ID. |
| get_video_jobB | Get a durable video job, including state, progress timeline, prompt compilation, output, and QC result. |
| list_video_jobsB | List recent durable video jobs. This is local job history, not a remote Drive search. |
| cancel_video_jobA | Request cancellation for a queued or active video job. It never starts another regeneration after cancellation. |
| refine_videoC | Create a new version from a prior job using a targeted creative directive while preserving unrelated approved details. |
| regenerate_videoC | Create a new version of a prior job from its approved creative brief. |
| recover_video_jobA | Self-healing recovery for a job whose Flow generation finished but whose download failed or was interrupted. Reattaches to the open Flow tab, retrieves the already-paid clip, removes the watermark, and completes the job. Never submits a new generation, so no additional credits are spent. |
| video_system_healthB | Check local video-job persistence, queue availability, and browser-session availability without exposing credentials. |
| download_flow_videoA | Legacy manual download from an authorized Google asset URL or Drive ID. Completed orchestration jobs already download and validate their own asset. |
| list_videosC | List all generated videos from Google Drive |
| gmail_searchC | Search Gmail using advanced query syntax (same as Gmail search bar) |
| gmail_readA | Read the full content of an email by its message ID |
| gmail_sendB | Send an email via Gmail with optional CC and BCC |
| gmail_replyC | Reply to an existing email thread |
| drive_listB | List files in Google Drive with optional folder, name, and type filters |
| drive_uploadC | Upload a local file to Google Drive |
| drive_downloadC | Download a file from Google Drive to a local path |
| drive_create_folderC | Create a new folder in Google Drive |
| drive_trashB | Move a file to trash in Google Drive |
| sheets_readC | Read data from a Google Sheets spreadsheet |
| sheets_writeA | Write data to a Google Sheets spreadsheet (overwrites existing data in range) |
| sheets_appendB | Append rows to the end of a Google Sheets spreadsheet |
| sheets_createC | Create a new Google Sheets spreadsheet |
| docs_createC | Create a new Google Docs document with optional initial content |
| docs_readB | Read the text content of a Google Docs document |
| docs_appendB | Append text to an existing Google Docs document |
| calendar_list_eventsC | List upcoming events from Google Calendar |
| calendar_create_eventC | Create a new Google Calendar event with optional attendees |
| calendar_update_eventC | Update an existing Google Calendar event |
| calendar_delete_eventC | Delete a Google Calendar event |
| flow_browser_loginA | Open the persistent browser profile at Google sign-in. Complete login manually; this MCP server never accepts, types, stores, or logs passwords, TOTP secrets, cookies, or one-time codes. |
| flow_browser_autopilotC | Compatibility alias for a bounded, persistent Flow video job. It requires a manually authenticated persistent browser session and never automates password or MFA handling. |
| flow_browser_check_sessionA | Check if the Google browser session is still valid and active. Returns the session state without navigating away from the current page. |
| flow_browser_generate_videoB | Compatibility alias for generate_video using the persistent job orchestrator. Requires a manually authenticated Google browser session. |
| flow_browser_actionC | Execute a Google Flow action through browser automation (create, edit, run, export) |
| flow_screenshotB | Take a screenshot of the current browser page (useful for debugging) |
| flow_browser_closeA | Close the browser automation session. Session data is preserved for next launch. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| workflows-list | |
| videos-gallery | |
| video-jobs |
TDQS
Scored across 45 tools
The set is dominated by near-duplicate generations: get_video_status is explicitly an alias for get_video_job, flow_browser_generate_video and flow_browser_autopilot are aliases for generate_video, and generate_video/regenerate_video/refine_video plus list_flows/create_flow/trigger_flow form clusters an agent can easily confuse. The 'legacy bridge workflow' vs 'Google Flow' distinction is only stated in descriptions and is easy to miss when selecting a tool, and flow_browser_action (create/edit/run/export) overlaps with nearly every generation tool.
All names are snake_case, but the ordering convention is split between noun_verb (calendar_delete_event, drive_create_folder, sheets_read) and verb_noun (list_flows, generate_video, download_flow_video). Worse, the 'flow_' prefix is overloaded to mean both legacy bridge workflows (create_flow, trigger_flow) and browser automation (flow_screenshot), so names actively mislead about what family a tool belongs to.
At 45 tools this is far past a comfortable surface, and a meaningful fraction are compatibility aliases (get_video_status, flow_browser_generate_video, flow_browser_autopilot) or legacy bridge tools that could be a separate server. The Google Workspace tools (Gmail, Drive, Sheets, Docs, Calendar) also inflate the set well beyond the server's stated Flow purpose.
The Flow video lifecycle is genuinely deep — generate, status, list, cancel, refine, regenerate, recover, health, plus capability discovery — so the core domain is well covered. However the Workspace half is partial (no Gmail delete/labels/thread listing, no Drive move/rename, no Docs update/delete), leaving scattered gaps that force workarounds.