AI video editing workflows: the curated library
Every workflow here is organised by the job you need done. Pick a cluster to see the workflows, then use the comparison page to choose a tool.
Agent bridges into your editor
If your team edits in DaVinci Resolve or Premiere Pro, an agent bridge lets an AI client drive that editor, or lets you hand timelines between tools. These are young and mostly show no sample output. Read the safety notes before you install any of them.
| Bridge | What it connects | Watch for |
|---|
| davinci-resolve-mcp (samuelgursky) | An MCP server that lets an AI client drive DaVinci Resolve through its Python scripting API, with a 37-tool compound server or a 389-tool granular server. MIT. | External scripting needs Resolve Studio. The README gives no demo output and says it was built with AI coding agents. |
| Adobe UXP Premiere Pro samples | Adobe's official sample plugins for the Premiere Pro UXP API. Apache-2.0. | Only three samples, no output shown, and a recent Premiere version is required. |
| OpenTimelineIO | An open interchange format and Python/C++ API for editorial timelines, with adapters for formats such as EDL and FCP XML. Apache-2.0. | Some adapters, such as AAF and FCPX, are separate plugins and fidelity varies by editor. Check per adapter. |
| premiere-pro-mcp (leancoderkavy) | A Premiere Pro MCP with 393 core tools across 60 modules and 24 guided workflows. MIT. | The UXP path is a preview. A very large tool list can use up an agent's context. |
| Adobe Premiere Pro MCP (hetpatel-11) | An MCP server with a 283-tool catalog that writes ExtendScript and runs it through a CEP panel in Premiere Pro. MIT. | Safety warning: it runs arbitrary ExtendScript and has telemetry on by default. Review the code before you install. CEP is a legacy surface that Adobe is replacing with UXP. |
The research found auto-editor can also export timelines to Premiere, Resolve and Final Cut, which is a simpler bridge when you only need cuts.
Page checked on Nov 4, 2026.