PremierPro MCP Server: edit in Adobe Premiere Pro over MCP
PremierPro MCP Server
An open MCP server lets Claude and Cursor drive Premiere Pro: timeline, captions, effects, export, a rough cut from a script
- 144 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The server changes the Premiere project: it cuts clips, applies effects and exports files to disk
- The `unsafe` profile opens arbitrary scripts, shell commands and file I/O
Install
- Works in
Manual install
Clone the repository, run `just install`, `just proto`, `just build` and `just install-panel`, then add the `./go-orchestrator/bin/premierpro-mcp` server to the MCP config with the `--transport stdio` arguments. Do not enable the `unsafe` profile without my permission.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The server changes the Premiere project: it cuts clips, applies effects and exports files to disk
- The `unsafe` profile opens arbitrary scripts, shell commands and file I/O
This is third-party code. Review the repository files before installing.
What it does
PremierPro MCP Server connects an MCP client to Adobe Premiere Pro through a CEP bridge on the local machine. From a script and a media folder it builds an edit decision list and assembles a rough cut on a duplicated sequence that can be recovered. The server registry holds 1,066 tool schemas, and the default `standard` profile exposes 74 curated, readback-first tools, which fits model function limits. They cover project and sequence inspection, import, placement, trimming, markers and export; script parsing and asset matching; a caption track from validated SRT; effects and transitions (12 ready recipes); MOGRT-based titles and social variants. Audited routes return an explicit `unsupported` error when Premiere cannot perform and confirm a change. Profiles such as `core`, `captions` and `social` narrow the set, `all` opens the whole safe catalogue, and arbitrary script, shell and file I/O tools appear only with the `unsafe` profile. Seven skills ship with it: dialogue cutting, captions, social reframing, transition recipes, effect chains, proxies and batch delivery.
Who it is for. Video editors and creators in Premiere Pro who hand routine to an agent: rough cuts from a script, captions, reframing and delivery variants.
Good fit when
- A rough cut must be assembled on a copy of the sequence from a script and a media folder
- A caption track must be made from a ready SRT and the caption count checked after the write
- Vertical and square versions of a video are needed for social media
- A list of effects and transitions should be applied to clips by recipe with duration checks
- Batch delivery in several formats is needed, with proxies for heavy footage
Not a fit when
- You need a different editing program: the server works only with Adobe Premiere Pro
- Premiere Pro 2020 or newer is not installed: the bridge has nothing to connect to
- You need every command guaranteed in your version: a schema's presence does not prove the command works everywhere
- You want public network access to the server: the SSE transport listens on the local address only and has no authorization
Example request
Edit a 5-minute video from script.pdf using the footage in /media/ on a duplicated sequence, and show the edit list before assembling.MCP
- Transport
- stdio, sse
- Authentication
- not required
Environment variables
MCP_TOOL_PROFILE- Tool set: standard by default, also core, captions, social, all or all,unsafe
Limitations
Building needs Go 1.26.1 or newer, Rust 1.85, Python 3.12, Node.js 20, `just`, `buf` and FFmpeg, and the CEP panel works on macOS and Windows only. There is no live matrix by Premiere version yet: the primary target is 25.x, and on 26.5.2 for macOS arm64 8 core workflows were tested.
The broad catalogue contains legacy and experimental handlers that did not pass the same audit. Run the host smoke test on your Premiere build before mutating a project. The bridge needs a shared token in `~/.premierpro-mcp/cep-token` and cannot run inside Docker.
How to disable. Remove the server from the MCP client configuration and delete the CEP panel from Premiere Pro's extensions folder. The bridge token is in `~/.premierpro-mcp/cep-token` and can be deleted.
FAQ
How do I connect the server?
Build with `just install`, `just proto` and `just build`, install the panel with `just install-panel` and add the `./go-orchestrator/bin/premierpro-mcp` command with `--transport stdio` arguments to your MCP client.
What is the standard profile?
It is a set of 74 curated tools that read state back after every mutation. Other profiles are set with the `MCP_TOOL_PROFILE` variable: core, dialogue, captions, social, transitions, effects, proxies, delivery or a combination.
Is it safe for a Premiere project?
Changes go onto a duplicated sequence, and timeline snapshots serve for comparison and are not a rollback of the whole sequence. For important projects, copy the project file beforehand.
Which Premiere Pro versions are supported?
The bridge manifest declares versions from 14.0 (2020). The primary development target is 25.x, and on 26.5.2 for macOS arm64 8 core workflows were tested. The full matrix is not ready yet.
How does it differ from other Premiere MCP servers in the catalogue?
This server comes with 1,066 schemas and tool profiles, an SRT caption track, transition recipes and seven editing skills. Other servers cover a smaller set of commands.
Discussion
No questions or reviews yet.
Related
MCP serversMCP for Adobe Premiere Pro: editing through an agent
MCP for Adobe Premiere Pro
A local MCP server that lets Claude, Cursor and Codex read a Premiere Pro project, edit the timeline and export the result
MCP server that drives local Adobe Premiere Pro projects from Claude, Codex and other MCP clients
MCP server and panel let an agent read an Adobe After Effects comp and build animation as ordinary editable layers and keyframes.
An MCP server for Adobe After Effects: build compositions, layers, keyframes and expressions through an agent
An After Effects panel with an MCP server: an agent reads the project, builds animations, checks frames and saves scripts
An MCP server connects an agent to a running Adobe After Effects: project inspection, layer edits, expressions and frame renders.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| PremierPro MCP Server: edit in Adobe Premiere Pro over MCP (this card) | no | not required | 144 | |
| MCP for Adobe Premiere Pro: editing through an agent | no | not required | 525 | another MCP server for Premiere with a smaller command set |
| DaVinci Resolve MCP | no | not required | 4,088 | a similar server for DaVinci Resolve, a different editing program |
README in short
The README explains the purpose, the verified boundary, supported Premiere versions, a four-language architecture and project structure. Then come prerequisites, quick start, MCP server setup, skills, platform launchers, CEP bridge security and build commands. The licence is MIT.