MCP Bridge for Adobe Premiere Pro

Operate local Adobe Premiere Pro projects through MCP.

284 tools, 13 context resources, and 10 guided prompts for Codex, Claude Code, Claude Desktop, and other MCP clients. CEP handles editing; the optional UXP helper reads Premiere Speech-to-Text transcripts.

Languages: English | 日本語 | Tiếng Việt | 简体中文 | 繁體中文 | 한국어 | Deutsch | Español | Français | Italiano | Dansk | Polski | Русский | Bosanski | العربية | Norsk | Português (Brasil) | ไทย | Türkçe | ភាសាខ្មែរ

Start here: install the local bridge, open it in Premiere, then run verify_premiere_connection before editing.

Install | Codex plugin | Claude Code plugin | Verify | Privacy Policy | Terms of Service | Security

Install

The supported bridge is the included CEP panel. Install the npm package on the same computer as Premiere Pro and your MCP client:

npm install -g @compimprove/adobe-premiere-mcp
premiere-pro-mcp --install-cep
premiere-pro-mcp --doctor

--install-cep installs the CEP bridge, enables the required Adobe CEP debug setting, prepares the bridge directory, and configures supported local MCP clients. --doctor verifies the server build, CEP installation, bridge directory, debug setting, and client configuration.

Then restart Premiere Pro, open Window > Extensions > MCP Bridge (CEP), set the bridge directory shown by the installer, and start the bridge.

Requirements:

• Node.js 20+

• Adobe Premiere Pro 2020+

• Premiere Pro, the MCP client, and this package on the same computer

The bundled uxp-plugin is an independent Premiere 25.6+ transcript helper. It does not replace the CEP editing bridge and is not installed by the CLI yet.

Codex plugin

From a clone of this repository, install the Codex plugin that bundles the MCP configuration and Premiere editing skill:

codex plugin marketplace add .
codex plugin add premiere-pro-mcp@adobe-premiere-pro-mcp

The plugin still requires the local CEP bridge. Run premiere-pro-mcp --install-cep, restart Premiere, start Window > Extensions > MCP Bridge (CEP), then ask Codex to run get_capabilities followed by verify_premiere_connection.

Claude Code plugin

From a clone of this repository:

/plugin marketplace add .
/plugin install premiere-pro-mcp@adobe-premiere-pro-mcp

Install and start the CEP bridge with the same steps as above before using the plugin.

Claude Desktop one-click bundle

Each GitHub release includes an .mcpb bundle for Claude Desktop. Download the matching adobe-premiere-pro-mcp-<version>.mcpb asset and open it in Claude Desktop to install the local MCP server. Its first launch installs the bundled CEP bridge for the current user.

Restart Premiere Pro, open Window > Extensions > MCP Bridge (CEP), set the bridge directory, and start the bridge. Then ask Claude:

Run verify_premiere_connection. Make no changes.

The MCPB bundle is unsigned. Install it only from this repository's GitHub Releases. CEP release archives are labeled accurately as unsigned or self-signed; self-signed does not mean Adobe Marketplace trusted.

MCP client configuration

The installer configures Claude Desktop on macOS and Claude Desktop plus GitHub Copilot in VS Code on Windows. For another MCP client, configure it to run:

{
  "mcpServers": {
    "premiere-pro": {
      "command": "premiere-pro-mcp"
    }
  }
}

Install from source

Use source setup when developing the MCP, modifying the CEP panel, or troubleshooting a package install:

git clone https://github.com/compimprove/adobe-premiere-mcp.git
cd adobe-premiere-mcp
npm install
npm run build
npm run setup:mac # macOS

On Windows, use npm run setup:win from PowerShell after npm install and npm run build.

Current CEP panel UI inside Premiere Pro, using the refreshed bridge controls and status layout.

Related MCP server: Premiere Pro MCP Server

Current Status

This repository is currently validated for:

• macOS

• Windows installer/config smoke checks through GitHub Actions

• Adobe Premiere Pro 2020+ (actively used and tested on Premiere Pro 26.0)

• Node.js 20+

• MCP v2 server transport with modern stateless protocol discovery

• the included macOS installer path for Claude Desktop

• the included Windows installer path for GitHub Copilot in VS Code and Claude Desktop config

• manual MCP registration for Codex, Claude Code, and similar MCP clients

Current catalog status as of August 5, 2026:

• 284 MCP tools are exposed for AI-driven video editing

• coverage spans project setup, media ingest, bins, sequences, timeline editing, transitions, effects, keyframes, captions, markers, metadata, proxies, multicam, color, audio, exports, and higher-level assembly workflows

• the catalog includes practical agent workflows such as product-spot assembly, motion-graphics demos, timeline razoring, caption reads, audio ducking, scene edit detection, EDL import, export readiness validation, and linked audio/video operations

Most recent completed local live validation:

• 284 active tools are exposed; get_capabilities reports local installation and optional live connection state, while verify_premiere_connection is the canonical read-only bridge and host readiness check

• 0 known parked or placeholder tools are advertised

• import_ae_comps is intentionally not advertised because Premiere returned false for real .aep fixtures in this environment and a generic .aep import can wedge the CEP bridge

The full live sweep output is written to /tmp/premiere-mcp-bridge/live-tool-sweep.json when you run the verifier.

What You Get

The server covers project operations, ingest, sequence creation, timeline editing, transitions, effects, keyframes, metadata, exports, and higher-level assembly workflows.

Example prompts:

• "List all sequences and show me which one is active."

• "Import these three shots and build a rough product spot."

• "Add cross dissolves to every cut on video track 1."

• "Apply Gaussian Blur to the middle clip."

• "Apply the Black & White effect to the active short-form clip."

• "Razor the interview sequence at 12.5 seconds across all audio and video tracks."

• "Export the active sequence as FCP XML."

For monochrome looks, prefer apply_effect with Black & White instead of trying to force black and white through generic saturation-only adjustments.

Before editing, you can also attach the premiere://config/get_instructions resource to give the model Premiere-specific operating guidance.

For a predictable start to every session, first run verify_premiere_connection. It confirms that the CEP bridge responded and returns the Premiere build, open project, and active sequence without modifying the project.

High-level workflow tools included:

• build_motion_graphics_demo

• assemble_product_spot

• build_brand_spot_from_mogrt_and_assets

assemble_product_spot and build_brand_spot_from_mogrt_and_assets now support an optional clipPlan argument so an LLM can direct per-clip timing, track placement, transitions, motion, trims, effects, and color adjustments instead of relying on fixed template defaults.

Agent Skill

If you want Codex, Claude Code, or another agent to handle installation, verification, and day-to-day usage correctly, install the included Agent Skill:

npx skills add compimprove/adobe-premiere-mcp --skill premiere-pro-mcp

Or install directly from the skill path:

npx skills add https://github.com/compimprove/adobe-premiere-mcp/tree/main/skills/premiere-pro-mcp

The skill teaches agents how to install the MCP, start and verify the CEP bridge, use the Premiere tools safely, import real media before editing, prefer sequence-aware operations, and run diagnostics when something fails.

Advanced Setup and Verification

For source installs, client-specific MCP configuration, Windows installer flags, diagnostics, and the live tool sweep, use QUICKSTART.md. It is the canonical setup guide and keeps this page focused on choosing and using the product.

The short version:

1. Install with npm install -g @compimprove/adobe-premiere-mcp, then run premiere-pro-mcp --install-cep.

2. Restart Premiere Pro and your MCP client, then start Window > Extensions > MCP Bridge (CEP).

3. Run premiere-pro-mcp --doctor, then ask the client to call verify_premiere_connection without making changes.

For manual registration in any MCP client, use the global command after npm installation:

{
  "mcpServers": {
    "premiere-pro": {
      "command": "premiere-pro-mcp"
    }
  }
}

CEP remains the editing bridge. If Premiere does not expose the extension, enable UXP Plugins > Enable developer mode in Premiere preferences, restart Premiere, and reopen the CEP panel. The separate UXP panel is required only for Speech-to-Text transcript reads.

For a real-host sweep, use a disposable Premiere project and run node scripts/live-tool-sweep.mjs; it creates temporary Sweep ... sequences in the current project.

For source installs that enable the optional transcript bridge, the setup also:

• install dependencies

• build dist/index.js

• enable Adobe CEP debug mode

• install the MCP Bridge (CEP) extension

• create /tmp/premiere-mcp-bridge

• prepare the UXP transcript command queue

• add the premiere-pro MCP entry to Claude Desktop

Important:

• MCP Bridge (CEP) remains the supported bridge for the existing editing tools

• MCP Transcript Bridge (UXP) is an optional helper used only by read_sequence_transcription

• the installer enables Adobe CEP debug mode automatically

• if Premiere does not expose the extension cleanly on your machine, enable UXP Plugins > Enable developer mode in Premiere Pro preferences before opening the bridge panel

• npm run setup:mac is the easiest path for Claude Desktop on macOS because it updates Claude Desktop config automatically

After the installer finishes:

1. Quit and reopen your MCP client if it reads config on startup. If you used the installer, that means Claude Desktop.

2. Quit and reopen Premiere Pro.

3. In Premiere Pro on macOS, open Premiere Pro > Preferences > Plugins and enable UXP Plugins > Enable developer mode.

4. Restart Premiere Pro if the setting was changed.

5. Open Window > Extensions > MCP Bridge (CEP).

6. Set Temp Directory to /tmp/premiere-mcp-bridge.

7. Click Save Configuration.

8. Click Start Bridge.

9. To enable transcription reading, load the repository's uxp-plugin folder in Adobe UXP Developer Tool, then open Window > UXP Plugins > MCP Transcript Bridge.

10. In the UXP panel, enter /tmp/premiere-mcp-bridge as the bridge root, click Save bridge root, then click Start Bridge.

11. Connect from Codex, Claude Code, Claude Desktop, or another MCP client using the same temp directory.

12. If CEP commands fail, click Run Diagnostics and send back /tmp/premiere-mcp-bridge/premiere-mcp-diagnostics-latest.json.

If you need a visual reference for the developer mode toggle, it looks like this:

If the panel reports that Premiere is ready after Start Bridge, the bridge is live.

Install By Client

Claude Desktop

On macOS, use:

npm run setup:mac

That is the only path in this repo that automatically writes the MCP entry for you.

Codex

Build the server first:

npm install
npm run build

Then add the MCP server on a single line:

codex mcp add premiere_pro --env PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridge -- node /absolute/path/to/Adobe_Premiere_Pro_MCP/dist/index.js

Claude Code

Build the server the same way:

npm install
npm run build

Then register the MCP server in Claude Code using the same built dist/index.js entrypoint and the same temp directory:

command: node /absolute/path/to/Adobe_Premiere_Pro_MCP/dist/index.js
env: PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridge

If you use a local MCP config file instead of a helper command, point it at the same dist/index.js and set the same env var.

Other MCP Clients

Use the same manual registration approach as Claude Code:

command: node /absolute/path/to/Adobe_Premiere_Pro_MCP/dist/index.js
env: PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridge

Important for all manual client setups:

• keep the command on one line

• use the real absolute path to dist/index.js

• restart the client after adding or updating the MCP entry

• start the CEP bridge inside Premiere and confirm the temp directory is exactly /tmp/premiere-mcp-bridge

• for read_sequence_transcription, also start the UXP Transcript Bridge with that same root folder

Verify the Install

Run the built-in checks:

npm run setup:doctor

That validates:

• Node.js version

• built server output

• CEP extension install

• /tmp/premiere-mcp-bridge

• Adobe CEP debug mode

• the Claude Desktop config entry when you use the installer path

• CEP panel diagnostics written to /tmp/premiere-mcp-bridge/premiere-mcp-diagnostics-latest.json

• UXP transcript-helper heartbeat at /tmp/premiere-mcp-bridge/uxp/status.json when the optional helper is running

For a deeper end-to-end check, use a disposable Premiere project and run:

node scripts/live-tool-sweep.mjs

This creates temporary Sweep ... sequences in the currently open project so the toolchain is exercised against real data.

How the Bridge Works

+-----------+        +-----------+        +-----------+
|  Client   |  MCP   | Node.js   | Files  | CEP Panel |
| (Codex+)  |<------>| MCP Server|<------>| edits     |
+-----------+        +-----------+        +-----------+
                                  |
                                  | Files: uxp/commands + uxp/responses
                                  v
                           +-----------+
                           | UXP panel |
                           | transcripts|
                           +-----------+

1. The client calls an MCP tool.

2. Existing editing tools generate ExtendScript and use the CEP panel's command files.

3. read_sequence_transcription writes a versioned UXP request to uxp/commands.

4. The UXP panel reads source-clip Speech-to-Text transcripts through Premiere's UXP API and writes a normalized response to uxp/responses.

5. The server returns structured JSON to the MCP client. CEP and UXP do not call one another.

Tools

All 284 advertised tools have an implementation. Tool schemas are available through MCP discovery; this catalog explains the editing surface in human terms. Start with verify_premiere_connection, then inspect the project before asking an agent to mutate it.

Discovery and project inspection

The catalog covers:

• Discovery and project inspection

• Project and sequence management

• Media import and bin management

• Timeline placement and clip operations

• Effects, transitions, color, and keyframes

• Markers, metadata, labels, and work-area control

• Export and interchange helpers

• MOGRT, captions, proxies, and relink helpers

• Speech-to-Text transcript reading (Premiere 25.6+ with the optional UXP helper)

• High-level ad / promo assembly workflows

Projects, media, and bins

Sequences and tracks

Timeline editing and trim operations

Effects, color, motion, and keyframes

Audio, transitions, and captions

Markers, selection, navigation, and playback

Delivery, interchange, and media management

Graphics, workflows, workspace, and advanced operations

Additional supported operations

The remaining catalog covers lower-level control of media properties, project settings, display formats, anti-aliasing, poster frames, color labels, selection, track targeting, project paths, and project counts. It includes set_override_frame_rate, set_override_pixel_aspect_ratio, set_frame_blend, set_time_interpolation, set_poster_frame, set_anti_alias_quality, set_uniform_scale, set_scale_width_height, set_sequence_display_format, set_project_scratch_disk, get_project_scratch_disks, get_all_project_paths, get_total_clip_count, get_insertion_bin, is_work_area_enabled, and match_frame.

Use MCP introspection in your client for each tool's exact input schema and return shape. An agent should inspect first, make a focused mutation, and read back the affected state before continuing a multi-step edit.

Real Limits

• A self-signed CEP .zxp confirms archive integrity but is not Adobe Marketplace approval or a public trust guarantee. The reproducible signing workflow requires private certificate secrets and target-platform Premiere validation.

This project is much more usable than the original prototype, but it is not magic.

• Premiere scripting still does not expose every UI operation cleanly.

• Caption tracks are not the same as Speech-to-Text transcripts: read_sequence_captions remains unavailable through CEP, while read_sequence_transcription reads source-clip transcripts through UXP.

• Professional title design still depends on real MOGRT assets or external graphics workflows.

• get_render_queue_status is only useful when Adobe Media Encoder integration is available.

• The best results come from real source footage, real audio, and real brand assets. The automation layer assembles and manipulates them; it does not replace editorial judgment.

Troubleshooting

If the tools are visible but calls fail:

1. Confirm Premiere Pro is open with a project loaded.

2. Open Window > Extensions > MCP Bridge (CEP).

3. Confirm the temp directory is exactly /tmp/premiere-mcp-bridge.

4. Click Start Bridge.

5. If you updated the bridge code, right-click the panel and choose Reload.

6. Retry the command.

If read_sequence_transcription reports that the UXP bridge is unavailable:

1. Use Premiere Pro 25.6 or later.

2. Enable Plugins > Enable Developer Mode, then load uxp-plugin with Adobe UXP Developer Tool.

3. Open Window > UXP Plugins > MCP Transcript Bridge.

4. Enter /tmp/premiere-mcp-bridge, click Save bridge root, then click Start Bridge.

5. Ensure the source clips in the sequence were transcribed in Premiere's Text panel. The tool returns a partial result when some source clips have no transcript.

If the MCP client cannot find the server:

1. Verify the absolute path to dist/index.js.

2. Verify PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridge.

3. Restart the MCP client after changing config.

4. Run npm run setup:doctor.

Developer Notes

Useful commands:

npm run build
npm test -- --runInBand
npm run setup:doctor
node scripts/live-tool-sweep.mjs

See:

• QUICKSTART.md for the shortest install path

• KNOWN_ISSUES.md for current limits

• CONTRIBUTING.md for development workflow