google-flow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOW_MCP_CDP_PORT | No | Port used for the Chrome DevTools Protocol connection. | 9333 |
| FLOW_MCP_LOG_LEVEL | No | Logging level for the MCP server. | info |
| FLOW_MCP_STATE_DIR | No | Directory for logs, screenshots, and job data. | ~/.google-flow-mcp |
| FLOW_MCP_CHROME_PATH | No | Path to the Google Chrome executable. | /Applications/Google Chrome.app/Contents/MacOS/Google Chrome |
| FLOW_MCP_USER_DATA_DIR | No | Directory where the dedicated Chrome profile and user data are stored. | ~/.google-flow-chrome |
| FLOW_MCP_GENERATION_TIMEOUT_MS | No | Timeout in milliseconds for generation operations. | 1800000 |
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 |
|---|---|
| flow_connectA | Attach to the dedicated Chrome (launching it if needed), open a tab owned by this server and load Google Flow. Other tools connect on demand, so this is mainly a warm-up and login check. If logged_in is false, sign in once in the Chrome window. |
| flow_statusA | Report browser connection, login state, the current Flow project/scene, the running tool and in-flight jobs. Never touches the page. |
| flow_screenshotA | Save a PNG of the tab this server owns and return its absolute path. Useful to see what the agent or Scene Builder is showing. |
| flow_inspectA | Snapshot interactive elements, optionally perform one action (click/hover a button matched by text or aria-label regex, press a key, or navigate), then return the elements that appeared/disappeared. This is how selectors are discovered when Flow changes its UI; paste the rows into a bug report. Never generates anything. |
| flow_project_openA | Navigate the owned tab to a Flow project URL and report how many media items the grid shows. Generation tools call this implicitly. |
| flow_generate_videoA | Generate one video through the Flow agent composer and download it. Spends Flow credits when auto_confirm=true. Call with auto_confirm=false first: the prompt, settings and reference image are prepared and verified but nothing is sent. resume=true skips the composer and only waits for / downloads an in-flight generation (after a crash or timeout). |
| flow_generate_imageA | Generate images through the Flow agent composer (Nano Banana models) and download them. Spends Flow credits when auto_confirm=true; auto_confirm=false prepares and verifies without sending. resume=true only waits for / downloads an in-flight generation. |
| flow_media_downloadA | Download one Flow media item (video or image) by its media id using the logged-in browser session. Ids come from the generation and scene tools or from flow_project_open. |
| flow_scene_addA | Open a project media item's menu and "Add to Scene → Create scene", then open the new Scene Builder view. Returns the scene URL to pass to flow_scene_extend / flow_scene_status / flow_scene_download. Costs no credits. |
| flow_scene_statusA | Open a Scene Builder view and report its clips (index, duration) and total length, plus whether an extension is still rendering. with_media_ids selects each clip to read its media id (slower). Costs no credits. |
| flow_scene_extendA | Scene Builder "Extend": generates a 7-second continuation of the clip at after_clip_index (must be the last clip) with Veo 3.1 - Lite and downloads it as a separate media file. Spends credits when auto_confirm=true; auto_confirm=false opens the extend prompt, fills it, takes a screenshot and cancels. Safe to retry: if the extension was already generated (clip present at after_clip_index+1, or resume=true after a crash) it is downloaded instead of generated again. |
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 11 tools
Each tool addresses a distinct part of the workflow: connection/status, page observation, project opening, generation, media download, and scene operations. Similar actions like generating a video versus extending a scene are clearly separated by context and dedicated names.
All tools share a useful flow_ prefix and consistent snake_case, but the word order is mixed: flow_generate_video is verb-object while flow_project_open, flow_media_download, and flow_scene_add are object-verb. This is still readable but does not follow a single predictable verb_noun pattern.
Eleven tools is well-scoped for the Google Flow domain, covering browser connection, inspection, project navigation, generation, downloads, and scene extension without redundancy. Each tool earns its place and the count is within the ideal range.
The core end-to-end workflows are covered: connect, open a project, generate video/image with confirmation and resume support, download media, and extend scenes. Minor gaps exist around enumerating projects or arbitrary media IDs without a prior URL or generation result, but these are workable.