MCP - the Model Context Protocol - is starting to show up in video tools because the review loop is full of exactly the work agents are good at: pulling notes out of one system, drafting candidates, and pushing results back. This is an honest map of what works today: what MCP actually is, what Frooty ships right now (local MCP bridges for Premiere Pro and DaVinci Resolve, agent-assisted planning and B-roll in beta), and what is still in development - no sci-fi.
What is MCP?
The Model Context Protocol is an open standard that lets AI applications call external tools through a uniform interface. Instead of every AI app hand-wiring every product's API, a product exposes an MCP server, and any MCP-capable AI client - Claude, and a growing list of others - can use its tools: read a comment list, fetch a project's versions, drive an editor action. The practical significance for post-production: the notes, the versions, and the NLE can finally talk to the same agent.
Why review tools are adopting it
Look at where a review round actually loses time: notes live in the review tool, the fix happens in the NLE, and a human shuttles between them - reading each comment, locating the moment, staging the fix, uploading the next version. Frame.io has started shipping an MCP beta of its own, which tells you the industry read is the same. The review loop is the natural agent seam: bounded data, concrete actions, and a human approval gate already built into the workflow.
What Frooty ships today
Being precise about status - some of this is beta:
- Local MCP bridges for Premiere Pro and DaVinci Resolve. Frooty's editor integrations expose MCP tools that let an AI agent work with your review data inside the NLE context. The Resolve bridge is a separate Lua MCP bridge that runs on both the free and Studio editions of Resolve; Premiere connects through the panel's tool set.
- Agent-assisted planning and B-roll (beta). Frooty's @auto and @agent flows can plan cuts and stage B-roll candidates for an editor to accept or discard.
- Hosted cloud MCP - in development. A hosted Frooty Cloud MCP server is on the roadmap; today the bridges are local to your editor setup.
Status summary
Live today: review links, frame-accurate comments, versions, watermarks, publishing. Beta: agent editing flows (@auto/@agent) and the local NLE MCP bridges. In development: hosted cloud MCP. Treat every agent claim in this space - ours and competitors' - as beta until you have run it on your own project.
An agent-assisted review loop, step by step
- Client leaves notes at exact frames on the review link - same as always.
- The editor opens the NLE and lets the agent (via the MCP bridge) pull the open threads for the current version.
- The agent stages candidates - B-roll options for the "middle feels empty" note, caption drafts for the copy note - each attached to the frame that triggered it.
- The editor approves, edits, or discards each candidate. The agent never ships anything on its own.
- The next version uploads, reviewers verify their notes were addressed, and the loop closes with the recorded approval.
What agents are good at - and what they are not
Good: retrieval across versions and comments, tedious scaffolding (pulling lists, staging options, drafting variants), and never getting tired of the ninth "can you also try" request. Not good: final creative judgment and anything that needs accountability. The approval stays a human event - which is not a limitation bolted on for safety; it is the workflow. See how the pieces fit in the AI agents review workflow guide and reviewing AI-generated video with clients.
Product pages: Frooty MCP and editor integrations.
FAQ
What is MCP in video editing?
MCP (Model Context Protocol) is an open standard that lets AI applications call a product's tools through a uniform interface. In video editing, it means an AI agent can read your review comments, fetch versions, and drive editor actions inside Premiere Pro or Resolve without custom integrations per app.
Does Frooty support MCP?
Yes - today as local MCP bridges for Premiere Pro and DaVinci Resolve (the Resolve bridge runs on free and Studio editions), with agent-assisted planning and B-roll in beta. A hosted Frooty Cloud MCP server is in development.
Which NLEs have Frooty agent bridges?
Premiere Pro and DaVinci Resolve today, via their respective MCP bridges; Final Cut Pro works through review links and FCPXML-based delivery rather than a live bridge.
Will AI agents replace editors?
No - and the workflow design tells you why. Agents are good at retrieval and staging candidates; editors hold creative judgment and accountability. The pattern that works is agent proposes, editor disposes, client approves.
What is the difference between MCP and an API?
An API is one product's custom interface; MCP is a shared protocol that many AI clients already speak. Exposing tools over MCP means every MCP-capable AI application can use them without you building a separate integration for each one.