Independent · open source · local bridge
Free, open-source bridge that connects AI assistants (Claude, Cursor, ChatGPT) to Adobe Premiere Pro. Make timeline edits, apply effects, and export—all with local-first privacy and explicit confirmation.
New here? Learn what Premiere Pro MCP is
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.24.1
Current release
macOS + Windows
Supported desktop hosts
Local-first
Media stays on your machine
MIT licensed
Source available on GitHub
Recorded in Premiere Pro
Watch three coastal clips become a 15-second sequence with review markers and a saved project. Recorded in Premiere Pro using original sample artwork.
Timeline
Three clips assembled
Finish
Review markers added
Delivery
Editable project saved
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 latest GitHub release and download its .mcpb bundle. Open it 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.
Get connector on GitHubFinish 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.
Install the correct package
Use the exact npm package name for this project:
npm i -g premiere-pro-mcp@1.24.1Name check: this project's package is premiere-pro-mcp, not adobe-premiere-pro-mcp. Both can expose a premiere-pro-mcp command, so confirm the package name before you configure a client.
Verify you have the right install
npm list -g premiere-pro-mcp
premiere-pro-mcp --versionExpect version 1.24.1. Homepage should be premiere-pro-mcp.com; source is github.com/leancoderkavy/premiere-pro-mcp.
Use this route if your assistant does not support a native bundle. It requires Node.js 20.19+.
npx --yes premiere-pro-mcp@1.24.1 --install-cep
npx --yes premiere-pro-mcp@1.24.1 --doctorOnly use this when your client asks for a command. Keep Premiere, the connector, and the client on the same computer.
{
"mcpServers": {
"premiere-pro-leancoderkavy": {
"command": "npx",
"args": [
"--yes",
"premiere-pro-mcp@1.24.1"
]
}
}
}Merge the entry into existing settings. It selects this project's versioned npm package instead of relying on the shared global command name.
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.
Want a deeper technical dive into the architecture?
Learn about file-based IPC, security model, and verification workflow.
Need the full tool list, schemas, or troubleshooting guide?
The README documents every setup path and known security boundary.
Common questions about AI automation for Adobe Premiere Pro: pricing, compatibility, privacy, installation, and supported AI assistants.
Read the complete documentationMCP for Adobe Premiere Pro is the independent, MIT-licensed local server published as premiere-pro-mcp. It connects compatible clients such as Claude, Cursor, and Codex to supported editing, inspection, media, and export tools. Check each tool contract before authorizing changes.
The MCP server and connector are free under the MIT license. Adobe Premiere Pro and your chosen AI client have separate requirements and costs.
Claude Desktop (recommended starting point with a self-contained bundle), Cursor, VS Code with GitHub Copilot, Windsurf, and any MCP-compatible AI client. The Premiere connector is installed separately and works with all supported clients.
You can automate timeline editing (insert, trim, split clips), apply effects and color correction, manage audio levels, create captions, organize project bins, import media, export sequences with Adobe Media Encoder presets, and inspect project metadata. Preview, approval, and undo behavior depend on the tool and host. Save a duplicate project and review returned outcome states before continuing.
The signed CEP connector works with Adobe Premiere Pro 2020–2026 on macOS (Apple Silicon and Intel) and Windows. The UXP bridge adds capability-gated workflows for Premiere 25.6.0+ hosts but is not the default installer.
No. The recommended setup is local-first: Premiere Pro, the MCP server, and the bridge all run on your machine. No project media is automatically uploaded. The bridge exchanges structured commands and results locally via private temp files. Your AI client's handling of prompts and tool results still applies. The optional UXP bridge uses an authenticated WebSocket.
For Claude Desktop: download the released bundle and the signed Premiere connector, restart both apps, and send a safe first prompt to verify the connection. For other AI clients: install via npm (premiere-pro-mcp), add the MCP config to your client settings, install the CEP connector, and restart. Full setup guides are available in the documentation.
A remote HTTP transport exists but requires authentication and a working connection back to the local Premiere Pro bridge. For most editors, the local setup is simpler, safer, and faster. Remote access is not designed for render farm deployments without local Premiere hosts.
Free · open source · local-first