Who it is forA creator who has built up work in a Flow project and wants a local copy before the project changes or runs out of space.
The problemWork made in Flow stays in the web project, and downloading each clip by hand or regenerating it costs time and credits.
The outcomeLocal copies of the project's media in ~/flow-mcp-out/, with each scene saved as one finished film and upscales included.
What you need first
- macOS or Windows 10/11
- Node.js 22 or newer
- Google Chrome
- A Google account (free tier gives 50 credits a day)
- A display that stays awake during runs
- FFmpeg (optional, only for joining clips, mixing music or recording narration)
- A Google AI Studio key (optional, only for Google narration voices)
Steps
- Run
git clone https://github.com/GTAI-1/flow-mcp.git, thencd flow-mcp, thennpm installandnpm run build. - Run
npm run loginand open the Flow project you want to archive in the Chrome window. - Run
claude mcp add --scope user flow -- node /absolute/path/to/flow-mcp/dist/index.jsand restart Claude Code. - Ask the assistant to list the project's assets, then download them with the free download tool.
- Check ~/flow-mcp-out/ for the downloaded files.
Prompt for your agent
Using the flow-mcp repo at <repo-path>, list the assets in the open Flow project and download all videos and images with the free download tool, including the 1080p upscale where available. Expected output is local media files in ~/flow-mcp-out/ with one stitched film per scene. Verify that the credits remaining shown by flow_status did not drop during the download.
Caveat. Full-quality downloads depend on your Google plan, since the README says a paid plan unlocks 1080p downloads.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page