MCP 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
- 455 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Any client that reaches the server gets control of the running Premiere and its projects
- A separate setting enables tools that run arbitrary code inside Premiere
- Installing the connector writes into Premiere's per-user extensions folder and switches on debug mode
Install
- Works in
Manual install
npm install -g premiere-pro-mcpNode.js 20.19 or newer is required. Then install the connector with premiere-pro-mcp --install-cep.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Any client that reaches the server gets control of the running Premiere and its projects
- A separate setting enables tools that run arbitrary code inside Premiere
- Installing the connector writes into Premiere's per-user extensions folder and switches on debug mode
This is third-party code. Review the repository files before installing.
What it does
The server connects an AI assistant to a running Adobe Premiere Pro through the documented UXP and CEP with ExtendScript interfaces. The agent inspects the project and sequences, imports media, lays clips on tracks, applies effects, works with keyframes and markers, and starts an export. The set holds 436 core tools, 29 guided workflows and four resources. The first check changes nothing: ask the assistant to call verify_premiere_connection. The tool reports whether the server is installed, the client is configured and Premiere is connected. Edits run in action modes, some operations need confirmation, and a response distinguishes a verified result from one that was accepted but not checked (committed_unverified). There are two install paths. For Claude Desktop use the ready .mcpb package, which already contains the server, plus the separately signed .zxp connector for Premiere. For other clients the server installs through npm and the connector with `premiere-pro-mcp --install-cep`. An additional UXP panel unlocks 96 more tools on a compatible version.
Who it is for. For video editors and automation developers who work in Premiere Pro 2020–2026 on Windows or macOS and want to hand project preparation, clip layout and export checks to an agent.
Good fit when
- You need an inventory of a project and sequence: tracks, clips, markers, a report with no edits
- Folders of footage must be imported and sorted into project bins by rules
- You need a working layout prepared: clips on tracks, transitions between them, markers for review
- You need review frames or an export check before sending to a client
- A finished After Effects render must be brought into an existing Premiere bin with a confirmation and an import receipt
Not a fit when
- Premiere Pro runs on a different computer from the client: the recommended setup keeps the assistant, server, connector and Premiere on one machine
- You need an exact result without human checking: some operations depend on the Premiere version and capabilities
- You need Premiere features closed to programmatic access, such as part of the AI features: the server reports what is available directly and what is not
- You have no copy of the project to try on: start on a duplicate
Example request
Check the Premiere Pro connection with verify_premiere_connection without changing anything, then list every sequence in the open project.MCP
- Transport
- stdio, http
- Authentication
- not required
Environment variables
PREMIERE_MCP_CAPABILITIES- List of enabled capabilities, for example inspect,edit,export,filesystem,unsafe-script
PREMIERE_CONTEXT_BACKEND- The value memory turns off keeping project context on disk
MCP_AUTH_TOKENsecret- Required for the HTTP transport; not needed with stdio
PREMIERE_UXP_TOKENsecret- A secret for the authenticated UXP panel connection
Limitations
Besides the server you need a separate connector for Premiere. You need Premiere Pro 2020–2026, Node.js 20.19 or newer for the npm install, and an open project with an active sequence. Trimming clips and slipping content needs FFmpeg with ffprobe on PATH: without it those edits refuse before the project changes.
The project is independent and not affiliated with Adobe. Support for individual tools depends on the system and Premiere version. A local run does not mean data stays out of the cloud: your AI client handles prompts and tool results under its own rules. Writing through the UXP panel needs the updated panel, otherwise it stays read-only.
How to disable. Remove the premiere-pro entry from your client configuration and uninstall the extension in Claude Desktop. Run npm uninstall -g premiere-pro-mcp and remove the connector through your ZXP installer or from Premiere's per-user extensions folder.
FAQ
How do I connect Premiere Pro to Claude Desktop through MCP?
Download the .mcpb package from the releases page and install it in Claude Desktop under Settings, Extensions, Advanced settings. Then open the signed .zxp connector with a ZXP installer, restart Premiere and open the Window > Extensions > MCP for Adobe Premiere Pro panel. This path needs no Node.js.
What do I need to install besides the MCP server itself?
The connector for Premiere: in the .zxp package or with premiere-pro-mcp --install-cep. It is copied into Premiere's per-user extensions folder and switches on debug mode. Trimming and slipping clips also needs FFmpeg.
Is it safe to let an agent control Premiere?
Any client that reaches the server controls Premiere. The execute_extendscript and evaluate_expression tools are hidden and disabled by default and turn on with the unsafe-script value in PREMIERE_MCP_CAPABILITIES. Start with verify_premiere_connection and work on a project copy.
How does this server differ from the adobe-premiere-pro-mcp package?
They are separate projects. This repository publishes only the premiere-pro-mcp package. The other package also declares a premiere-pro-mcp executable, so check the package name and repository with npm list -g premiere-pro-mcp and premiere-pro-mcp --version.
Does the server run on Windows and macOS and with which Premiere versions?
Yes, on both, with Premiere Pro 2020–2026. The assistant, server, connector and Premiere must be on one computer, and the set of available tools depends on the system and version.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server that drives local Adobe Premiere Pro projects from Claude, Codex and other MCP clients
An MCP server for Adobe After Effects: build compositions, layers, keyframes and expressions through an agent
An MCP server for video editing built into the free Concat editor: the agent cuts clips, adds titles and captions, sets keyframes and exports video
DaVinci Resolve MCP
DaVinci Resolve MCP Server
An MCP server that drives DaVinci Resolve Studio through the official scripting API: editing, media pool, rendering, grading and Fusion
An MCP server for Adobe Photoshop: background removal, retouch, social export and batch jobs by chat
VidMoat MCP
Vidmoat MCP
Remote MCP server of a cloud video editor: an agent imports footage, edits the timeline, checks frames and renders MP4
README in short
The server can also be deployed on Fly.io, and the architecture keeps two bridges: CEP with ExtendScript and UXP. The project has a site with a demo and a comparison of servers, under the MIT license.