Skip to main content
Glama

Google Flow MCP (V2 Controller)

Self-hosted Model Context Protocol (MCP) server for Google Flow (labs.google/fx/tools/flow), refactored into a lean controller for book and story asset generation pipelines.

Authenticate with your own Google account to generate character candidates, props, places, scenes, and video clips—saving all outputs directly to your local file system or external drive (/Volumes/Xstorage/...).


Production Workflow Architecture

This MCP operates strictly as a controller for Google Flow asset creation:

Approved dossier
→ create book project
→ Storyboard Studio
→ characters / places / props / scenes
→ download candidates
→ approve stills
→ Veo / Omni animation
→ download clips
→ MiniMax
→ Remotion / CapCut
NOTE

This MCP server is a thin Google Flow controller layer. It doesNOT handle full dossier truth systems, final trailer scripting strategy, MiniMax orchestration, Remotion assembly, CapCut rendering, or video publishing. Those operations belong outside this repository in the primary Immerse pipeline.


Related MCP server: flow-mcp

Key Principles & Scope

  • 🎯 Google Flow Controller: Pure control layer for authenticating, listing/creating projects, executing Storyboard Studio/custom tools, generating media, and downloading assets locally.

  • 🔒 Spend Guard & Budget Safety: Video generation tools (generate_video and generate_video_from_image) strictly require confirm_spend: true to prevent accidental credit consumption. Supports max_credits and max_generations limits.

  • 📂 Local Storage Integration: Auto-scaffolds clean book folder structures (/characters, /props, /places, /scenes, /clips) on local or external drives.

  • 🤝 Pipeline Handoff: Decoupled from final trailer editing or assembly. Assets are saved cleanly for handoff to external tools (MiniMax, Remotion, CapCut).

  • 🔐 Isolated Auth & Safety: Session credentials are kept strictly isolated and stored locally with restricted 0600 file permissions.


Installation & Setup

1. Build Server

git clone https://github.com/LeoSzn12/google-flow-mcp.git
cd google-flow-mcp
npm install
npm run build

2. Environment Configuration

Copy .env.example to .env:

cp .env.example .env

Set your session credentials and local output root:

GOOGLE_COOKIES="your_google_cookies_string"
LOCAL_STORAGE_ROOT="/Volumes/Xstorage/Media"

Available MCP Tools (V2)

Core Control Tools (14)

Tool Name

Description

Key Parameters

flow_status

Check authentication state & account details

account

connect_google_account

Save Google auth cookies or tokens

cookies, bearerToken

list_projects

List Google Flow projects on your account

-

create_project

Create a new Google Flow project

name

list_tools

List custom tools in a project

project_id

run_custom_tool

Execute custom tool or Storyboard tool

tool_id, project_id, prompt, inputs

generate_image

Generate image via NARWHAL / Nano Banana

prompt, model, aspect, output_folder

generate_images_batch

Batch generate image candidates

prompts, model, aspect, output_folder

generate_video

Text-to-video via Veo 3.1 (Spend Guard)

prompt, confirm_spend (required), max_credits, max_generations, output_folder

generate_video_from_image

Image-to-video keyframe animation (Spend Guard)

prompt, start_image_url, confirm_spend (required), max_credits, max_generations, output_folder

check_job_status

Query status of async generation jobs

job_id, project_id

save_media_to_local_folder

Save generated media URL or ID to local disk

media_url_or_id, output_folder, filename

list_media

List all generated media items in session memory

-

get_media_details

Get details for a specific media item

media_id

Thin Helper Tools (2)

Tool Name

Description

Key Parameters

create_book_project

Scaffold local book folder structure on disk

book_title, local_storage_root

run_storyboard_studio_from_dossier

Execute Storyboard Studio with dossier input

dossier_text, book_title, asset_types, output_folder


Integration Guides

Claude Code / Codex

claude mcp add --transport stdio google-flow -- node /absolute/path/to/google-flow-mcp/dist/index.js

Cursor / Windsurf / Cline (mcpServers)

Add to ~/.cursor/mcp.json or .vscode/mcp.json:

{
  "mcpServers": {
    "google-flow": {
      "command": "node",
      "args": ["/absolute/path/to/google-flow-mcp/dist/index.js"],
      "env": {
        "GOOGLE_COOKIES": "your_google_cookies_string_here",
        "LOCAL_STORAGE_ROOT": "/Volumes/Xstorage/Media"
      }
    }
  }
}

Happy Path Example Workflow (The Odyssey)

Here is how to run a complete asset pipeline workflow for an example book (The Odyssey):

1. Create a Book Project & Local Storage Folders

Call create_book_project:

{
  "book_title": "The Odyssey",
  "local_storage_root": "/Volumes/Xstorage/Media"
}

Creates /Volumes/Xstorage/Media/the-odyssey/ with subfolders: characters/, props/, places/, scenes/, clips/.

2. Run Storyboard Studio with an Approved Dossier

Call run_storyboard_studio_from_dossier:

{
  "book_title": "The Odyssey",
  "dossier_text": "Odysseus: Weathered ancient Greek king and mariner, dark curly hair, bearded, wearing bronze-trimmed linen tunic, standing on rocky shore looking out at Aegean Sea.",
  "asset_types": ["characters", "places", "scenes"],
  "output_folder": "/Volumes/Xstorage/Media"
}

Generates visual candidates and downloads stills directly into local project subfolders.

3. Animate Approved Keyframes into Video Clips

Call generate_video_from_image with explicit spend authorization:

{
  "prompt": "Slow panning shot across Aegean sea waves crashing on rocky cliffs behind Odysseus",
  "start_image_url": "/Volumes/Xstorage/Media/the-odyssey/characters/odysseus_still.png",
  "confirm_spend": true,
  "max_credits": 20,
  "max_generations": 1,
  "output_folder": "/Volumes/Xstorage/Media/the-odyssey/clips"
}

Renders video using Google Veo 3.1 and saves flow_video_<timestamp>.mp4 to /clips.

4. Immerse Production Handoff

Hand off downloaded .png stills and .mp4 video clips to external assembly tools (MiniMax, Remotion, CapCut).


License

MIT

Available Tools

22 tools
audit_custom_toolA

Audit the capabilities, parameters, models, and code logic of a Google Flow custom tool.

Inputs: tool_id (required).

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.

Inputs: prompts (required), model, aspect, account.

connect_google_accountA

Connect or update Google account credentials for Google Flow generation.

Inputs: cookies, bearerToken.

create_characterB

Create a reusable character card with consistent visual traits across multiple scenes.

Inputs: name (required), description (required), model.

flow_statusA

Check Google Flow connection status, active plan, remaining credits, and daily limits.

Inputs: account.

generate_from_dossierB

Generate high-fidelity artwork and scenes derived directly from an uploaded dossier (e.g. ACOTAR Feyre & Rhysand in Velaris).

Inputs: scene, aspect, prompt, character, +1 more.

generate_imageB

Generate a high-fidelity AI image using Google Flow (Nano Banana / NARWHAL models). Runs on your Google account.

Inputs: prompt (required), seed, count, model, +3 more.

generate_storyboardB

Create a multi-frame visual sequence using Google Flow Storyboard Studio tool.

Inputs: scenes (required), title.

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.

Inputs: book_title (required), dossier_title, target_platform, target_duration_seconds.

generate_videoA

Generate an AI video from text using Google Flow (Veo 3.1 / Gemini Omni models).

Inputs: prompt (required), count, aspect, account, +2 more.

generate_video_from_imageA

Animate a static image into an AI video (Image-to-Video) using Google Veo 3.1.

Inputs: prompt (required), aspect, account, start_image_url, +2 more.

generate_with_faceA

Generate a new image featuring a saved character card to maintain face/subject consistency.

Inputs: prompt (required), character (required), aspect.

get_media_detailsA

Get detailed information about a specific generated media item.

Inputs: media_id (required).

list_mediaB

List all generated images and videos in the current session.

Inputs: no named parameters.

list_projectsA

List all Google Flow projects available on your account.

Inputs: no named parameters.

list_toolsB

List all custom tools available in a Google Flow project.

Inputs: project_id.

render_approved_trailer_videosA

Render the final Veo 3.1 video clips from approved storyboard keyframes and download them to your local media folder.

Inputs: approved_shots (required), output_folder.

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.

Inputs: tool_id (required), inputs, prompt, project_id.

save_media_to_local_folderA

Save/download a generated image or video URL to a local folder on your computer.

Inputs: media_url_or_id (required), filename, output_folder.

update_custom_toolB

Edit or update the code, prompt instructions, or parameters of a custom Google Flow tool directly inside Google Flow.

Inputs: tool_id (required), name, project_id, description, +2 more.

upload_dossierC

Upload a character/worldbuilding dossier (such as ACOTAR characters, lore, and visual rules) to Google Flow.

Inputs: title (required), content, tool_id, dossier_path.

upscale_imageA

Upscale an image generated via Google Flow to high resolution (1K, 2K, 4K).

Inputs: media_id (required), target_resolution (required), account.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 22 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers