google-flow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP transport | 3000 |
| TRANSPORT | No | Server transport (stdio or http) | stdio |
| GOOGLE_COOKIES | No | Google session cookies for auth | |
| GOOGLE_BEARER_TOKEN | No | Alternative OAuth bearer token | |
| GOOGLE_FLOW_TOOL_ID | No | Google Flow tool ID | 947d22df-da9a-4e3c-bef9-f4af87e0b60d |
| GOOGLE_FLOW_PROJECT_ID | No | Google Flow project ID | b2cffabf-8a98-4710-a852-d01a4dae1f74 |
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_statusA | Check Google Flow connection status, active plan, remaining credits, and daily limits. |
| connect_google_accountA | Connect or update Google account credentials for Google Flow generation. |
| generate_imageB | Generate a high-fidelity AI image using Google Flow (Nano Banana / NARWHAL models). Runs on your Google account. |
| generate_videoA | Generate an AI video from text using Google Flow (Veo 3.1 / Gemini Omni models). |
| generate_video_from_imageA | Animate a static image into an AI video (Image-to-Video) using Google Veo 3.1. |
| upscale_imageA | Upscale an image generated via Google Flow to high resolution (1K, 2K, 4K). |
| create_characterB | Create a reusable character card with consistent visual traits across multiple scenes. |
| generate_with_faceA | Generate a new image featuring a saved character card to maintain face/subject consistency. |
| run_custom_toolB | Execute a custom or shared Google Flow tool (e.g. Type Overlays, Video Resizer, Storyboard Studio, Shader Effects, Mockup, etc.) by tool ID or full URL. |
| upload_dossierC | Upload a character/worldbuilding dossier (such as ACOTAR characters, lore, and visual rules) to Google Flow. |
| generate_from_dossierB | Generate high-fidelity artwork and scenes derived directly from an uploaded dossier (e.g. ACOTAR Feyre & Rhysand in Velaris). |
| generate_storyboardB | Create a multi-frame visual sequence using Google Flow Storyboard Studio tool. |
| save_media_to_local_folderA | Save/download a generated image or video URL to a local folder on your computer. |
| update_custom_toolB | Edit or update the code, prompt instructions, or parameters of a custom Google Flow tool directly inside Google Flow. |
| audit_custom_toolA | Audit the capabilities, parameters, models, and code logic of a Google Flow custom tool. |
| generate_trailer_scriptA | Generate a viral 30-45 second social media (TikTok/Reels) cinematic book trailer script and storyboard keyframes for human review and approval. |
| render_approved_trailer_videosA | Render the final Veo 3.1 video clips from approved storyboard keyframes and download them to your local media folder. |
| list_mediaB | List all generated images and videos in the current session. |
| batch_generate_imagesA | Generate multiple images in a single batch call using Google Flow Nano Banana Pro. More efficient than calling generate_image multiple times. |
| list_projectsA | List all Google Flow projects available on your account. |
| list_toolsB | List all custom tools available in a Google Flow project. |
| get_media_detailsA | Get detailed information about a specific generated media item. |
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 22 tools
While most tools target distinct actions, several image/video generation tools (generate_image, batch_generate_images, generate_with_face, generate_from_dossier) overlap in the core generation action and could cause misselection. Storyboard generation also overlaps with the trailer script tool. However, the descriptions do differentiate inputs and use cases.
Tool names predominantly follow a verb_noun pattern (e.g., generate_image, list_projects, update_custom_tool). Minor variations like generate_with_face, generate_from_dossier, and save_media_to_local_folder deviate but remain readable and predictable.
At 22 tools, the server is on the heavier side of the recommended range. The breadth is justified by the mix of generation, character/dossier management, custom tool operations, and trailer workflow, but it still feels slightly over-scoped.
The tool surface covers the core media generation lifecycle, including account management, image/video generation, upscaling, character consistency, dossier-based generation, custom tool management, and media retrieval/saving. Missing operations are primarily deletion (e.g., no delete_character or delete_media) and character listing, but these are minor gaps.