flow-mcp
An MCP server through which an agent makes frames and videos in Google Flow under your Google account
- 380 ★ on the repository
- Last commit
Broad access
Why this level
- The program signs in as your Google account and clicks buttons on the Flow site; the documentation does not discuss the service's rules for such automation
- Shooting video spends your account credits
- The local panel and API listen on 127.0.0.1 and are protected by a token in ~/.flow-mcp/token
Install
- Works in
Manual install
npm install && npm run buildAfter git clone https://github.com/GTAI-1/flow-mcp.git into the home folder. Then run npm run login once and sign in to Google in the window that opens.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The program signs in as your Google account and clicks buttons on the Flow site; the documentation does not discuss the service's rules for such automation
- Shooting video spends your account credits
- The local panel and API listen on 127.0.0.1 and are protected by a token in ~/.flow-mcp/token
This is third-party code. Review the repository files before installing.
What it does
flow-mcp lets Claude, Codex or another MCP client work with the Google Flow site on your computer. The program opens a dedicated Chrome window with its own profile, signs in as you and clicks Flow's real buttons. No browser extension is needed, and there is no hosted service or extra sign-up. The agent creates characters and draws key frames. Then it shoots clips of several seconds with pinned first and last frames, and it can restyle finished videos. Before spending credits you can set a ceiling with the max_credits parameter: the price comes from Flow's own quote, and a scene that costs more is skipped. Flow draws images for free, and only video consumes credits. With FFmpeg the server joins clips and mixes music and narration, and with whisper.cpp it makes captions on your computer. The same features work without an agent in a local panel started with `npm run studio`.
Who it is for. For short-video makers and developers who have a Google account with Flow access and want to run production from Claude or Codex.
Good fit when
- You need a series of clips with one character: stills first, then shooting with a credit cap per scene
- You need to join finished shots into a film with narration and music
- You need captions for a video in styles like Bold pop or Word by word, computed locally
- You want to re-download Flow project media, including the 1080p version, without spending more credits
Not a fit when
- You need a headless or server run: the Chrome window is really driven, so a display must stay awake
- You work from ChatGPT: its connectors reach only servers on the internet, while flow-mcp runs on your computer
- You need a paid video API: the project drives the site's interface and uses no API
- You need a guarantee on Windows: the author developed on macOS and has not yet run Windows on a real PC
Example request
Check my Flow session, create a character called Pip, a small lamplighter in a flat cartoon style, and draw three stills with himMCP
- Transport
- stdio
- Authentication
- not required
Limitations
Requires macOS or Windows 10 or 11, Node.js 22 or newer, Google Chrome and a Google account. Flow gives 50 credits a day for free, and a paid Google AI plan adds credits and 1080p. FFmpeg is needed for joining and audio, whisper.cpp for captions and a Google AI Studio key only for Google voices. The author developed the project with Claude and has not tested Codex or Antigravity. The repository has no license file. On macOS the project folder must not live in Desktop, Documents or Downloads.
How to disable. Remove the flow server from your client's MCP settings, for example with claude mcp remove flow. The Chrome profile holding your sign-in lives in ~/.flow-mcp/chrome-profile; delete that folder to erase the saved session.
FAQ
How do I connect flow-mcp to Claude Code?
Build the project and sign in to Google with `npm run login`, then run `claude mcp add --scope user flow -- node /absolute/path/flow-mcp/dist/index.js`. The `--scope user` flag makes the server available in every folder.
What does it cost to use Flow through flow-mcp?
Flow draws images for free. Video spends account credits: 50 a day on any Google account, with a paid Google AI plan adding more.
Does the program see my Google password?
No. You sign in yourself in a dedicated Chrome window, and the program only uses the session you created. The profile is stored in ~/.flow-mcp/chrome-profile, separate from your everyday browser.
Can I work without an AI agent?
Yes. `npm run studio` opens a local panel at 127.0.0.1:8787 with tabs for characters, frames, shots, voice, cutting and captions.
Which MCP tools does flow-mcp provide?
The main ones are flow_status, flow_generate and flow_wait: the first shows the session and credits, the second queues scenes, the third collects results. The other tools cancel and repeat jobs and list, download and delete project media.
Discussion
No questions or reviews yet.
Related
MCP serversA command-line client and MCP server for Google Flow: Veo video and Imagen images from the terminal, in batches or from agents
ClipForge MCP
ClipForge
ClipForge MCP builds a vertical video from a topic or a product link: stock footage, Edge TTS voiceover and captions, no keys, composed with FFmpeg
Claude Video Vision
claude-video-vision
An MCP server and Claude Code plugin that let the agent watch video: frames via ffmpeg and audio transcription via Gemini, local Whisper or OpenAI
Skills, a CLI and an MCP server that let Claude Code or Codex make video from a brief: editing, graphics, voiceover, subtitles
VidMoat MCP
Vidmoat MCP
Remote MCP server of a cloud video editor: an agent imports footage, edits the timeline, checks frames and renders MP4
An MCP server for video editing built into the free Concat editor: the agent cuts clips, adds titles and captions, sets keyframes and exports video
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| flow-mcp (this entry) | no | not required | 380 | |
| Visual Skills | no | 599 | writes prompts for video and image generation but does not run the shoot itself | |
| ima2-gen | no | 889 | a local studio for images and video through several providers, without Google Flow |
README in short
The README opens with a diagram: the MCP client talks to flow-mcp over stdio, and flow-mcp drives a Chrome window with Flow through the Chrome DevTools Protocol. Requirements, installation, a six-step first film, panel tabs and a tool table follow.