Credentials. Google voices need a Google AI Studio key, which the panel stores on your computer, so keep it out of chats and shared folders.
Who it is forA creator with finished Flow clips who needs a spoken narration and background music in one local MP4.
The problemRecording narration and mixing it with several clips usually means separate tools and paid voice services.
The outcomeOne MP4 in ~/flow-mcp-out/ with the clips joined in order, a narration track on top, and the clips' own sound turned down.
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
- Install FFmpeg with
brew install ffmpegon a Mac, orwinget install Gyan.FFmpegon Windows. - Run
git clone https://github.com/GTAI-1/flow-mcp.git, thencd flow-mcp, thennpm installandnpm run build. - Run
npm run studioand open http://127.0.0.1:8787 in your browser. - On the Voice tab, record a narration in a Google voice or your computer's own voice.
- On the Cut tab, pick your clips in order, add the narration and music, and turn the clips' sound down before exporting.
Prompt for your agent
Using the flow-mcp repo at <repo-path>, record the narration text <narration-text> with the free engine, then join the clips in <clip-folder> in order under that narration with background music. Expected output is one MP4 in ~/flow-mcp-out/. Verify that the file plays and the narration is audible over the lowered clip sound.
Caveat. Google narration needs a free Google AI Studio key, and the Mac voice option needs no key, so pick the engine that matches your setup.
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