Google Flow Browser MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flow_connectA | Launch Chrome with the configured Google profile, connect CDP, navigate to Google Flow, and verify account. |
| flow_disconnectA | Close the browser and clean up the MCP connection to Google Flow. |
| flow_statusB | Check current connection status: browser connected, Flow page loaded, account verified, job queue state. |
| flow_account_checkA | Verify the logged-in Google account matches the configured expected email (Default). |
| flow_discover_uiA | Navigate to a Google Flow page and discover all interactive elements (buttons, inputs, links, headings). Updates the internal selectors map for robust automation. |
| flow_generate_imageA | ⚠️ THESE IMAGES CONSUME CREDITS. By default (auto_confirm=false): fills the prompt, selects model/ratio, takes a screenshot and returns "ready_for_confirmation". Does NOT click Generate. When auto_confirm=true: first verifies the UI is in IMAGE mode (not Video), that the model is an image model, takes a verification screenshot, THEN clicks Generate and waits for the images. NANO/BANANA image models only. |
| flow_generate_videoA | Set up a video generation in Google Flow. Fills prompt, selects Omni Flash or Veo model, configures settings. NOTE: Does NOT click final Generate (paid feature — stops at ready-to-generate). |
| flow_download_latestB | Download the most recently generated file from Google Flow. |
| flow_create_characterA | Create a new character in Google Flow Characters with name and description. By default (auto_confirm not false), fills the description and clicks the submit arrow to actually create the character, then renames "Untitled Character" to the given name. |
| flow_import_characterA | Import a character from a saved JSON file into Google Flow. |
| flow_open_charactersB | Open the Characters page for the current/target project and list existing characters. |
| flow_list_mention_optionsA | List the images and characters in the current project that can be referenced via "@name" in an image/video prompt (opens Flow's "@" reference popup and reads its options). |
| flow_create_sceneB | Create a new scene in Google Flow Scenes with characters and prompt. |
| flow_open_tools_galleryA | Open the Google Flow Tools Gallery and list available tools. |
| flow_use_grid_architectA | Open Grid Architect in Google Flow, fill theme prompt, shot prompts, engine, ratio, and visual logic settings. Supports batch shot generation for brand campaigns. |
| flow_use_toolB | Open any tool by name in Google Flow and optionally fill its configuration parameters. |
| flow_screenshotB | Take a screenshot of the current Google Flow page. |
| flow_queue_statusA | Check the job queue: active job, pending queue, completed and failed job history. |
| flow_queue_resetA | Forcefully reset the job queue. Use this if a job is permanently stuck in "running" state and blocking other generations. |
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 19 tools
Tools are mostly distinct, covering connection, generation, characters, scenes, queue, and UI automation. Minor overlap exists between flow_status and flow_queue_status (both report queue state), and flow_use_tool vs flow_use_grid_architect (specialized case), but descriptions and parameters generally disambiguate clearly.
All tools share the 'flow_' prefix and use snake_case, with a predominantly verb-noun pattern (e.g., flow_generate_image, flow_create_character). A few object-led names like flow_account_check, flow_queue_status, and flow_queue_reset deviate from the verb-first convention, but the overall pattern remains readable and predictable.
With 19 tools, this is on the heavier side but justified by the broad scope of Google Flow automation: connection, media generation, character/scene management, queue control, and UI discovery. The count feels appropriate for the range of capabilities, though it approaches the threshold where complexity can become unwieldy.
Core workflows are covered, but there are notable gaps: no update/delete for characters or scenes, no list-scenes tool (while list-characters exists), and video generation stops short of triggering the final generation, leaving a dead end. Generic flow_use_tool and flow_discover_ui offer workarounds, but the surface is not fully self-sufficient for entity lifecycle management.