Google Flow Browser MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOW_URL | No | Base Google Flow URL. Corresponds to `flowUrl`. | https://flow.google.com/ |
| FLOW_HOME | No | Overrides the server's home/config directory location. | |
| FLOW_CDP_PORT | No | Chrome DevTools Protocol port. Corresponds to `cdpPort`. | 9222 |
| FLOW_HEADLESS | No | Run Chrome headless (not recommended — Flow needs a visible browser). Corresponds to `headless`. | false |
| FLOW_CHROME_PROFILE | No | Chrome profile folder name (e.g. `Default`, `Profile 1`). Corresponds to `chromeProfile`. | Default |
| FLOW_JOB_TIMEOUT_MS | No | Watchdog: max time a job may stay `running` before auto-fail. Corresponds to `jobTimeoutMs`. | 300000 |
| FLOW_EXPECTED_ACCOUNT | Yes | Google account email that `flow_account_check` expects. Corresponds to the required `expectedAccount` field in `config/flow.config.json`. | |
| FLOW_CHROME_EXECUTABLE | No | Full path to the Chrome executable (optional, auto-detected per-OS). Corresponds to `chromeExecutable`. | |
| FLOW_CHROME_USER_DATA_DIR | No | Path to Chrome's "User Data" folder (optional, auto-detected per-OS). Corresponds to `chromeUserDataDir`. |
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_openA | Navigate the already-connected browser to a Google Flow URL without reconnecting. Only https://flow.google.com/... URLs are allowed (other hosts rejected). |
| 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_uiB | 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_videoB | Prepare a Veo video (prepare-only, no spend). Fast tests, Quality finals; ingredients need 8s. |
| flow_list_modelsA | List video/image models, ratios, durations from Flow UI (live) or cache. Call once per session before generating. |
| 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=false): fills the description and returns "ready_for_confirmation" without submitting (no credits). When auto_confirm=true: fills and clicks submit, 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. By default (auto_confirm=false) prepares only; set auto_confirm=true to actually create. |
| flow_open_tools_galleryA | Open the Google Flow Tools Gallery and list available tools. |
| flow_use_grid_architectB | Open Grid Architect in Google Flow, fill theme prompt, shot prompts, engine, ratio, and visual logic settings. Supports batch shot generation for brand campaigns. Prepare-only by default (auto_confirm=false). |
| flow_use_toolB | Open any tool by name in Google Flow and optionally fill its configuration parameters. Prepare-only by default (auto_confirm=false). |
| 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 21 tools
Most tools have a clearly distinct resource or action (status, connect, generate_image, create_character, etc.), so an agent can usually tell them apart. However, flow_use_tool overlaps with specific wrappers like flow_use_grid_architect, and flow_status partially duplicates flow_queue_status and flow_account_check.
All tool names use a consistent flow_ prefix plus snake_case verb/noun structure. The convention is predictable throughout the set.
21 tools is heavy for a single browser-automation server and lands in the borderline range per the rubric. While many operations are justified, some could be consolidated or deferred, especially generic flow_use_tool versus specific tool wrappers.
Core lifecycle operations are present: connect/disconnect, navigate, discover UI, generate image, create characters/scenes, and queue status/reset. But there are notable gaps: flow_generate_video is prepare-only with no execute path, and there are no update/delete operations for characters/scenes or listing generated assets beyond the latest download.