MCP FOR ADOBE PREMIERE PRO DOCUMENTATION

AI editing tools for Adobe Premiere Pro

MCP for Adobe Premiere Pro is an open-source, local-first Model Context Protocol server that connects AI assistants to Adobe Premiere Pro through 349 structured editing, inspection, automation, and export tools.

Start without developer setup

The default route has two parts: your AI assistant gets a local server, and Premiere gets a separate connector. Claude Desktop is the recommended first route because the released bundle contains the server.

  1. Download the Claude Desktop bundle and open it in Claude Desktop.
  2. Download the signed Premiere connector. This is separate from the assistant bundle.
  3. Restart Claude Desktop and Premiere, then open a project.
  4. Send this read-only first prompt: Safely check my Premiere connection with verify_premiere_connection. Make no changes.

Cursor, VS Code / Copilot, and other MCP clients can use the supported local route too. A native one-click install for those clients is not currently shipped; use their MCP settings or the Advanced setup below.

Advanced: npm and manual configuration

This route requires Node.js 20.19+ and is intended for clients without a native bundle.

npm install -g premiere-pro-mcp
premiere-pro-mcp --install-cep
{
  "mcpServers": {
    "premiere-pro": { "command": "premiere-pro-mcp" }
  }
}

What can an AI assistant do in Premiere Pro?

Timeline editing

Insert, overwrite, move, trim, split, ripple-delete, target tracks, and inspect sequence structure.

Effects and color

Apply effects, control Lumetri properties, add keyframes, use LUTs, and verify resulting values.

Media and projects

Import footage, organize bins, create sequences, inspect metadata, manage proxies, and save projects.

Audio and captions

Adjust verified audio levels, automate keyframes, mute tracks, create captions, and inspect audio state.

Export

Discover Adobe Media Encoder presets, export sequences and project items, and verify frame output on disk.

Inspection and workflows

The server registers 349 core tools. The default profile exposes 347; a connected UXP panel exposes 440 capability-gated tools.

Windows, macOS, CEP, and UXP compatibility

The signed CEP connector is the default compatibility route for Premiere Pro 2020–2026 on Windows and macOS. The UXP bridge is capability-gated for compatible Premiere Pro 25.6+ workflows, but is not currently a Creative Cloud Marketplace install or a replacement for CEP. Compatibility is not the same as a live connection: use the safe first prompt before running a workflow.

Local-first architecture and security

The recommended local setup keeps Premiere Pro, the MCP server, and project media on the local computer. The first prompt runs a connection check, makes no edit, and does not ask for footage to be uploaded. Your chosen AI assistant's privacy settings still apply. Capability profiles separate inspection, editing, export, filesystem access, and unsafe scripting; raw ExtendScript is disabled by default and requires explicit operator authority.

Project context: a reviewable editing workflow

The opt-in local project-context engine is designed for repeatable work that needs more evidence than a conversational request. It never captures context until the MCP client asks for it, and it does not send an entire Premiere project or customer footage into every model turn.

  1. Use manage_project_context to capture a bounded active-sequence snapshot locally.
  2. Use search_project_context to retrieve only relevant evidence and stable identities.
  3. Use create_context_edit_plan to generate a non-mutating candidate scaffold with stale-state guards.
  4. Use preview_edit_plan before apply_edit_plan. Apply requires the exact preview confirmation token and current target validation.

A context plan is evidence, not mutation authority or proof that an editorial choice is correct. Clear local context when it is no longer needed.

Read the project-context engine guide

Canonical resources