MCP server that drives Google Flow (Veo / Nano Banana) through its internal tRPC API, with a hard credit-cost gate
An MCP server that lets an agent drive Google Flow (labs.google's Veo video / Nano Banana image tool) — with a hard credit-cost gate so it cannot quietly spend your money.
Flow has no public API. This server does not work around that by blindly clicking buttons: Flow's frontend is a tRPC client, so an undocumented API exists, and this speaks that API first. Clicking is the fallback, not the interface.
Status: v0.1, uncalibrated. Everything compiles, 33 unit tests pass, and the tool surface loads — but the DOM selectors and the tRPC endpoint map have not yet been re-verified against live Flow from this codebase. Run the calibration in First run before trusting it with credits; all three steps are free. See Verification status for exactly what is and is not proven.
- Why it is built this way - Transport ladder - Install · Connect a browser · Register with Claude Code - First run - Tools · Feature coverage - Examples · Credit reference - Verification status · Security - Architecture deep-dive · Contributing · Changelog
Read ARCHITECTURE.md for the full reasoning. The short version:
- Flow's UI is an agent-chat, not a form. You send a request, Flow's agent proposes a generation with a quoted credit cost, and nothing is charged until you approve. So the right design reads the quote and decides — it never fires and reconciles afterwards. - Rejecting a proposal is free. flowestimatecost is therefore not an estimate; it is the real price, at zero cost. - Stills are free, video is real money. The tools are shaped around the workflow that yields accepted clips at minimum spend:
From the project README.
Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:
[](https://mcp.liqiwa.com/s/roshanarnav25-sloth--google-flow-mcp.html)
MCP server for adding inline, range-anchored comments to Google Docs — the one comment operation the Google Docs & Drive APIs can't do. For AI agents (Claude, Cursor, Copilot) that review documents.
Gowthaman90/mcp-bastionReliability + security proxy for the Model Context Protocol (MCP): self-healing connections, runtime tool-security (rug-pull/poisoning detection), and a compliance-mapped audit trail.
luckeyfaraday/frontier-orchestratorMulti-agent orchestration for Claude Code: MCP server + skill that keeps Claude as lead engineer while delegating backend work to OpenAI Codex and frontend/design work to Kimi
kanetran29/uigraphYour app generates its own verified UI transition graph — screens as nodes, guarded (event, effect) edges. Proof-gated verification, trust tiers, model-free MCP for AI agents.
rayhankhilji/jellybeanA token-frugal MCP server that gives coding agents structural understanding of a codebase: repo maps, symbol outlines, ranked search, import tracing, and parsed diagnostics — every result under a toke
Anil-matcha/seedance-2.5-mcpSeedance 2.5 Preview MCP server powered by MuAPI.
The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.