Open source · local bridge · explicit confirmation
Connect the MCP-compatible client you already use to a local Premiere bridge. Review the target and plan first, then confirm supported work with current project state.
Project context is opt-in and local. Applied plans require current targets and confirmation.
Illustrated product workflow
A local project-context workflow makes the request inspectable from first evidence to returned result. This maps real MCP tools; it is not a recording of a live Premiere session.
manage_project_context
Read-only · opt-in local index
Create a bounded local snapshot of the active sequence and source identities.
v1.14.8
Current release
macOS + Windows
Supported desktop hosts
Local-first
Media stays on your machine
MIT licensed
Source available on GitHub
Illustrated product walkthrough
See the intended request-to-result flow. This animation is not a recording of a live Premiere host session.
Timeline
B-roll inserted on V2
Finish
Grade and title applied
Delivery
ProRes export queued
Give an MCP-compatible client structured operations instead of asking it to infer state from Premiere's interface.
Insert, overwrite, trim, split, move, ripple-delete, roll, slide, and slip across sequences and tracks.
Apply effects, adjust Lumetri parameters, load LUTs, stabilize clips, and automate repetitive grading steps.
Add, update, and inspect keyframes with interpolation controls for repeatable animation work.
Import footage, manage bins, create sequences from presets, inspect metadata, and work with proxies.
Queue sequences and project items through Adobe Media Encoder using the presets you choose.
Use the structured MCP surface or run custom ExtendScript and QE DOM workflows when you need deeper control.
Pick your client. The first step only checks that it can reach Premiere; it makes no edits.
Claude Desktop
Open the downloaded bundle in Claude Desktop. It includes the local server, so this path does not ask you to install Node just to connect Claude.
This separate CEP connector is what lets your assistant talk to Premiere. Open the download with a trusted ZXP installer; if your computer has none, use the npm installer under Advanced setup.
Download connector packageFinish the route above, then fully close and reopen both your assistant and Premiere.
Open a project and use the read-only prompt below. It runs the connection check and makes no changes.
Once the connection check passes, try a preview before applying any edits.
Safe first prompt
Safely check my Premiere connection with verify_premiere_connection. Make no changes.
Use this route if your assistant does not support a native bundle. It requires Node.js 20.19+.
npm install -g premiere-pro-mcp
premiere-pro-mcp --install-cepOnly use this when your client asks for a command. Keep Premiere, the connector, and the client on the same computer.
{
"mcpServers": {
"premiere-pro": {
"command": "premiere-pro-mcp"
}
}
}
A local-first file bridge keeps the control path inspectable and avoids exposing your project media to the MCP server.
Claude, Cursor, Windsurf, or another MCP client sends a structured request to the local server.
A versioned helper library and small ES3 script pass through a private shared temp directory.
The CEP bridge executes the command and sends structured data, confirmation, or diagnostics back to the client.
The signed CEP connector is the default route for Premiere Pro 2020–2026 on macOS and Windows. A modern UXP bridge adds capability-gated workflows on compatible newer hosts.
The CEP bridge creates its temp directory and starts polling when Premiere activates.
In-flight heartbeats help distinguish an open Premiere dialog from a disconnected bridge.
Know the boundary: UXP is capability-gated for compatible newer Premiere workflows; it is not yet the default installer or a replacement for CEP. Premiere’s undocumented QE DOM is powerful but imperfect, so results should be verified before you rely on them.
Need the full tool list, schemas, or troubleshooting guide?
The README documents every setup path and known security boundary.
Straight answers about compatibility, privacy, AI clients, and remote access.
Read the complete documentationMCP for Adobe Premiere Pro is an open-source Model Context Protocol server that gives compatible AI clients a structured set of tools for editing timelines, applying effects, managing media, and exporting from Adobe Premiere Pro.
The signed CEP connector is the default route for Adobe Premiere Pro 2020–2026 on macOS and Windows, including Apple Silicon and Intel Macs. The UXP bridge adds capability-gated workflows on compatible Premiere 25.6+ hosts; it is not the default installer.
The recommended setup is local-first. Premiere Pro, the connector, and the MCP server run on your machine, and the bridge exchanges commands and structured results rather than automatically uploading project media. Your AI assistant’s separate privacy settings still apply.
Claude Desktop has a released self-contained bundle and is the recommended starting point. Cursor, VS Code / Copilot, Windsurf, and other MCP-compatible clients can use the local server route. A native one-click installer for every client is not currently shipped.
A remote HTTP transport is available, but it requires authentication and a working connection back to the local Premiere Pro bridge. For most editors, the local setup is simpler and safer.
Free · open source · local-first
Connect your assistant, verify the local bridge without making changes, then preview the first edit before you apply it.