google-flow-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 (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 | 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_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 have clearly distinct purposes, such as connection management, generation, and character/scene creation. Minor overlap exists between flow_status and flow_account_check, and flow_use_tool may overlap with specialized tool openers, but descriptions are sufficient to disambiguate.
All tools share the flow_ prefix, but verb styles vary: some use verb_noun (generate_image, create_scene), others are bare verbs (connect, disconnect), and others are noun-first (status, queue_status, account_check). This mixed pattern reduces consistency.
At 17 tools, the count is slightly above the ideal 3-15 range but justified by the breadth of features (connection, generation, characters, gallery, UI automation). The set is not bloated, but a few could be consolidated.
The toolset covers major workflows: connect, generate, create characters/scenes, manage queue, and download. However, there are no update/delete operations for characters or scenes, no scene listing, and no way to list all generated files, leaving some lifecycle gaps.