Google Flow MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOW_CDP_PORT | No | CDP port of the dedicated browser | 9222 |
| FLOW_MCP_HOME | No | Config, outputs, logs and job store location | ~/.google-flow-mcp/home |
| FLOW_EXPECTED_ACCOUNT | No | Gmail address that must be signed in to Flow; unset skips the check |
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 (Profile 3). |
| 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 | ⚠️ CES IMAGES CONSOMMENT DES CRÉDITS. Par défaut (auto_confirm=false): remplit le prompt, sélectionne le modèle/ratio, prend un screenshot et retourne "ready_for_confirmation". NE clique PAS sur Generate. Quand auto_confirm=true: vérifie d'abord que l'interface est bien en mode IMAGE (pas Vidéo), que le modèle est un modèle image, prend un screenshot de vérification, PUIS clique Generate, attend les images et les télécharge. NAN/BANANA modèles image seulement. |
| flow_generate_videoA | ⚠️ CONSUMA CREDITI FLOW (Veo/Omni). Con auto_confirm=false (default): prepara il prompt video e si ferma senza generare (nessun credito). Con auto_confirm=true: invia, attende il render (minuti) e scarica l'mp4. Modello economico per test: "lite" (Veo 3.1 Lite). |
| flow_download_latestB | Download the most recently generated file from Google Flow. |
| flow_create_characterC | Create a new character in Google Flow Characters with name and description. |
| flow_import_characterB | Import a character from a saved JSON file into Google Flow. |
| flow_open_charactersA | Open the Google Flow Characters page and list existing characters. |
| 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_toolA | 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. |
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 17 tools
Most tools target distinct operations, but there is some overlap between flow_status and flow_queue_status, and flow_use_tool potentially overlaps with specific tools like flow_use_grid_architect or flow_open_tools_gallery. However, the descriptions generally clarify the intended boundaries.
All tool names follow a consistent flow_ prefix with snake_case verb/noun structure (e.g., flow_connect, flow_generate_image, flow_create_character). There are no mixed conventions or confusing naming patterns.
At 17 tools, the set is slightly heavy but still reasonable for a browser automation server covering connection, UI discovery, generation, characters, scenes, and queue monitoring. Most tools appear to earn their place, though a few could potentially be consolidated.
Core workflows like connection, generation, and character/scene creation are covered, but there are notable gaps such as no update/delete operations for characters or scenes, no explicit scene listing, and no job cancellation or cleanup tool beyond disconnection. These omissions could limit full lifecycle management.