Adobe Premiere Pro MCP Bridge

Community

Operate local Adobe Premiere Pro projects through MCP

★ 578 Stars Category · Other Very popular

54FMRS · D

This is a bridge that exposes local Adobe Premiere Pro projects to MCP clients, covering the chain from project inspection, media ingest, and timeline editing to effects, keyframes, audio, captions, exports, and delivery validation. It uses progressive tool discovery, advertising only a small always-on set by default to save context. The supported path is the CEP panel while UXP remains experimental, and the server must run on the same computer as Premiere and the MCP client, with installation touching CEP extensions and client config. Users should understand the risks of destructive tools and arbitrary script execution, and note that anonymous telemetry is on by default.

Reliability

9/20

Security and permissions

8/20

Maintenance

11/20

Documentation

14/20

Setup experience

12/20

Read the FMRS scoring method →

A local MCP bridge for Adobe Premiere Pro. It connects to Premiere through a CEP panel (the supported production bridge) or an experimental UXP panel, and exposes 283 Premiere tools, 13 context resources, and 10 guided prompts to Codex, Claude Code, Claude Desktop, and other MCP clients. A small always-on set (search_tools, get_tool_schema, invoke_tool, verify_premiere_connection, list_sequences) is advertised by default; call search_tools then invoke_tool for the rest, or set PREMIERE_MCP_TOOLSET=full to list all 283 tools. The Node server turns tool calls into ExtendScript written to /tmp/premiere-mcp-bridge, the CEP panel polls that directory and runs scripts via CSInterface.evalScript(), and the results come back as structured JSON.

Tools

search_tools

Search the 283-tool catalog with a BM25 query or a regex pattern.

get_tool_schema

Fetch the full input schema for one tool.

invoke_tool

Call any catalog tool by name with arguments.

verify_premiere_connection

Canonical read-only bridge and host readiness check returning Premiere build, open project, and active sequence.

list_sequences

List all sequences in the current project.

get_capabilities

Report local runtime capabilities and the catalog.advertised vs catalog.tools difference.

get_project_info

list_project_items

get_active_sequence

list_sequence_tracks

get_sequence_settings

get_full_project_overview

get_full_sequence_info

get_full_clip_info

search_project_items

find_project_item_by_name

find_items_by_media_path

get_timeline_summary

get_timeline_gaps

get_used_media_report

get_offline_media

check_offline_media

get_unused_media

get_duplicate_media

get_clip_properties

get_clip_speed

get_clip_at_position

get_clip_at_playhead

get_premiere_state

get_version_info

ping

create_project

open_project

save_project

save_project_as

close_project

import_media

import_folder

import_image_sequence

import_fcp_xml

import_sequences_from_project

import_sequences

create_bin

rename_bin

delete_bin

create_smart_bin

move_item_to_bin

move_items_to_bin

rename_project_item

rename_clip

delete_project_item

delete_multiple_project_items

create_subclip

refresh_media

relink_media

replace_clip_media

get_metadata

set_metadata

get_xmp_metadata

set_xmp_metadata

get_footage_interpretation

set_footage_interpretation

set_color_label

get_color_label

set_project_panel_metadata

create_sequence

create_sequence_from_preset

create_sequence_from_clips

duplicate_sequence

delete_sequence

close_sequence

set_active_sequence

get_sequence_structure

get_sequence_count

set_sequence_settings

set_sequence_frame_rate

set_sequence_resolution

set_sequence_audio_settings

set_sequence_pixel_aspect_ratio

set_sequence_field_type

add_track

add_tracks

delete_track

rename_track

lock_track

toggle_track_visibility

set_target_track

set_all_tracks_targeted

get_track_info

get_target_tracks

get_sequence_in_out_points

add_to_timeline

add_to_timeline_batch

insert_from_source

overwrite_from_source

overwrite_clip

remove_from_timeline

remove_selected_clips

ripple_delete

move_clip

Setup

On the same computer as Premiere Pro, install the npm package: npm install -g adobe-premiere-pro-mcp.
Run premiere-pro-mcp --install-cep to install the CEP bridge, enable the required Adobe CEP debug setting, and configure supported local MCP clients.
Run premiere-pro-mcp --doctor to verify the server build, CEP installation, bridge directory, debug setting, and client configuration.
Restart Premiere Pro, open Window > Extensions > MCP Bridge (CEP), set the bridge directory shown by the installer, and start the bridge.
Restart your MCP client; for manual registration, configure it to run the premiere-pro-mcp command.
Ask the client to call verify_premiere_connection without making changes.

Requirements: Node.js 20+, Adobe Premiere Pro 2020+, and Premiere, the MCP client, and this package on the same computer.

claude_desktop_config.json

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

Generate and validate client config

Fit and risk

Best for

Editors already using Premiere Pro who want to drive editing with natural language
Users who need repeatable, scripted batch operations in Premiere
Developers using MCP clients such as Codex, Claude Code, or Claude Desktop
Teams chaining ingest, timeline work, and delivery checks into agent workflows

Not for

Users without a local Premiere Pro install or who cannot run Node.js 20+
Cloud or remote-machine setups, since Premiere, the client, and this package must be on the same computer
Users expecting fully automatic professional-grade finished edits with no editorial judgment
Users needing Adobe-official support or Marketplace-certified plugins, as CEP archives are unsigned or self-signed

Required permissions

Read and write the /tmp/premiere-mcp-bridge bridge directory
Write the ~/.premiere-mcp-bridge/config.json configuration file
Install a CEP extension on the user's machine and enable the Adobe CEP debug setting
Modify local MCP client configuration such as Claude Desktop and GitHub Copilot in VS Code
Read and write local Premiere projects, media files, and exported files
Invoke local ffmpeg when detect_silence is used
Send anonymous usage telemetry by default (install id, OS, package version, tool name, success or failure)

Risks and side effects

Tools really modify the Premiere project; deletions such as delete_project_item, delete_multiple_project_items, and remove_from_timeline are irreversible unless undone promptly.
Advanced tools such as execute_extendscript and evaluate_expression can run arbitrary script and must only be used with trusted inputs and explicit intent.
A self-signed or unsigned CEP archive only confirms archive integrity; it is not Adobe Marketplace approval or a public trust guarantee.
The MCPB bundle is unsigned and should only be installed from this repository's GitHub Releases.
Anonymous telemetry is on by default; project names, media paths, arguments, and results are not sent, and it can be disabled in the panel or with PREMIERE_MCP_TELEMETRY=0.
Premiere scripting does not cover every UI operation; some results may be quantized or rejected by the host and should be read back for verification.
The bundled UXP panel is an experimental preview and is not a replacement for the validated CEP bridge.

Troubleshooting

Tools visible but calls fail: confirm Premiere Pro is open with a project loaded.
Open Window > Extensions > MCP Bridge (CEP) and click Start Bridge.
Confirm the temp directory is exactly /tmp/premiere-mcp-bridge.
After updating bridge code, right-click the panel, choose Reload, then retry.
Client cannot find the server: verify the absolute path to dist/index.js and PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridge.
Restart the MCP client after changing config, and run npm run setup:doctor or premiere-pro-mcp --doctor.
If Premiere does not expose the extension, enable UXP Plugins > Enable developer mode in Premiere preferences, restart Premiere, and reopen the CEP panel.
Run verify_premiere_connection first; it makes no changes to the project.

Use cases

Let an MCP client inspect the current project, media inventory, and sequences for edit planning

Import media, create bins and sequences, and place clips on the timeline in bulk

Cut, move, and trim clips and add transitions such as cross dissolves

Apply effects, keyframes, color correction, and LUTs to clips

Set clip volume, pan, and build ducking curves

Export sequences as FCP XML, AAF, OMF, or hand them to Media Encoder

Find offline, unused, or duplicate media before an edit or export

Run high-level workflows like assemble_product_spot to assemble product or brand edits

Supported clients

Claude DesktopFull support

Claude CodeFull support

CodexFull support

GitHub Copilot in VS CodePartial support

CursorPartial support

Related MCP servers

Compare with other MCP servers