Adobe Premiere Pro MCP Bridge

Community

Operate local Adobe Premiere Pro projects through MCP

How to install ↓ Compare GitHub source repository ↗

Category: Other #119 of 230
Stars: ★ 804 Very popular
Transport: stdio (local process)
Runtime: Node.js 20+
Credentials: No credential needed
License: MIT
Last commit: 8 days ago
Tools: 100

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.

Strongest · Documentation 14/20 Weakest · Security and permissions 8/20

Reliability

9/20

Security and permissions

8/20

Maintenance

11/20

Documentation

14/20

Setup experience

12/20

Why each score

Reliability 9/20: The README claims all 283 catalog tools have implementations, documents a local live sweep written to /tmp/premiere-mcp-bridge/live-tool-sweep.json, and ships scripts/live-tool-sweep.mjs, so a real-host per-tool verification path appears to exist; the architecture (Node server emits ExtendScript into a temp dir, CEP polls and evals it via CSInterface, results written back as JSON) is coherent and self-consistent. It also discloses known host gaps honestly: no scripting API to remove effects, caption text often unreadable via DOM, import_ae_comps deliberately unadvertised because a generic .aep import can wedge the bridge, render-queue status only meaningful with Adobe Media Encoder, UXP is experimental. However, this review is static: no cached server manifest, no source files, no CI workflows were supplied, so MCP init handshake, tools/list output matching the README table, and 283-tool counts cannot be confirmed; no committed unit tests covering key paths are visible; and reliability depends on external conditions (CEP debug setting, fixed /tmp path, specific Premiere builds). Under the static cap of 12, deducted to 9 for missing verifiable execution evidence.
Security and permissions 8/20: No red line: no Adobe/MCP credentials are requested, no real tokens appear in install examples, and the only network surface is opt-in-to-disable anonymous telemetry plus update checks with four documented opt-outs (panel checkbox, config.json flag, PREMIERE_MCP_TELEMETRY=0, DO_NOT_TRACK=1). The disclosed payload is limited to install id, OS, version, tool name, success/failure, duration, error code, and failing Zod field names, explicitly excluding project names, media paths, arguments, and results. Real risks remain: the catalog grants extremely broad host control, including delete_project_item, ripple_delete, clearContents, execute_extendscript, evaluate_expression, and inspect_dom_object, yet only advisory 'inspect first, mutate small' guidance is documented, with no mandatory confirmation or scoping for destructive tools; the bridge uses a fixed world-readable /tmp/premiere-mcp-bridge directory, a same-machine trust boundary; the installer enables Adobe CEP debug mode and the distributed MCPB/CEP archives are unsigned, requiring user trust in the download source. Main risks are visible but confirmation and scoping are incomplete, so 8.
Maintenance 11/20: Not archived, MIT licensed, versioned on npm with GitHub Releases, has update checking with in-panel upgrade prompts, and ships KNOWN_ISSUES, CONTRIBUTING, PRIVACY, TERMS, and SECURITY governance files; macOS is stated as validated while Windows is only smoke-tested via GitHub Actions, and 20 translated READMEs plus an Agent Skill indicate sustained investment. 578 stars corroborate activity but add no points. Missing evidence: no commit history, cadence, issue-response SLA, dependency-update automation, or concrete security-response channel is visible in the supplied material; the status of 19 open issues is unknown; the '283 tools as of Aug 31, 2026' claim cannot be verified; and the reproducible signing workflow depends on private certificate secrets, so outsiders cannot reproduce it. Active but with governance and version-consistency gaps: 11.
Documentation 14/20: Documentation is unusually layered: global npm install, --install-cep/--doctor, Claude Desktop .mcpb bundle, Codex and Claude Code plugin marketplaces, source install with macOS/Windows branches, and a generic mcpServers JSON; tools are grouped into themed tables with plain-language descriptions; there is a recommended first call (verify_premiere_connection), a premiere://config/get_instructions resource, a 'Real Limits' section, troubleshooting trees for both bridge and client failures, a telemetry field disclosure with opt-outs, update behavior, and explicit labels distinguishing production CEP from experimental UXP and unsigned MCPB/CEP artifacts. Deductions: no per-tool parameter schemas or return-shape examples (users are told to introspect), critical setup detail is offloaded to QUICKSTART.md which was not provided, self-consistency of numeric claims (283 all implemented, import_ae_comps unadvertised) rests on unverified source, and there is no cost or performance guidance. 14.
Setup experience 12/20: The mainstream-client path looks clear: two npm commands plus --doctor, restart Premiere, open Window > Extensions > MCP Bridge (CEP) and Start Bridge, then use Claude Desktop, Codex, Claude Code, or VS Code Copilot; ready-made mcpServers JSON, per-client plugins, and a one-click MCPB bundle are provided, with macOS and Windows branch scripts. But evidence is thin: the installer enables an Adobe CEP debug setting (a host-level side effect), the bridge directory must be exactly /tmp/premiere-mcp-bridge and match what the panel shows, and without executing anything the success rate of --install-cep on real machines is unverifiable; Windows is smoke-tested only; the UXP panel additionally needs developer mode. Troubleshooting steps such as verifying the absolute dist/index.js path and setting PREMIERE_TEMP_DIR indicate a fairly manual, fragile fallback. Under the static cap of 15, scored 12.

Static review · not runListed 2026-09-18

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesWrites / deletes local filesRuns commands or code

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.

Setup

Before you start

Runtime：Node.js 20+

Other optional settings (5)

PREMIERE_MCP_TELEMETRY optional Set to 0 to opt out of anonymous usage telemetry (also possible via the CEP panel, config., or DO_NOT_TRACK).

PREMIERE_MCP_TOOLSET optional Set to full to advertise all 283 tools via tools/list; by default only a small always-on set is listed.

PREMIERE_TEMP_DIR optional Overrides the CEP bridge file-exchange directory, which defaults to /tmp/premiere-mcp-bridge.

PREMIERE_MCP_UPDATE_CHECK optional Set to 0 to disable the update check.

DO_NOT_TRACK optional Set to 1 to opt out of anonymous telemetry.

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"
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

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

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add premiere-pro -- premiere-pro-mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After starting the MCP Bridge (CEP) panel in Premiere, call verify_premiere_connection from your MCP client; if it returns the Premiere build, open project, and active sequence, the bridge is working.

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.

Things to try

Once connected, you can ask your AI assistant things like:

Run verify_premiere_connection and tell me the open project and active sequence without making any changes.
List all sequences in the current project and show the media items in the project panel.
Import these three video files into the project, then create a sequence and add them to the timeline.
Add cross dissolves to every cut on video track 1.

Tools 100

search_tools read-only

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

get_tool_schema read-only

Fetch the full input schema for one tool.

invoke_tool writes

Call any catalog tool by name with arguments.

verify_premiere_connection read-only

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

list_sequences read-only

List all sequences in the current project.

get_capabilities read-only

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

get_project_info read-only

list_project_items read-only

Show 92 more tools

get_active_sequence read-only

list_sequence_tracks read-only

get_sequence_settings read-only

get_full_project_overview read-only

get_full_sequence_info read-only

get_full_clip_info read-only

search_project_items read-only

find_project_item_by_name read-only

find_items_by_media_path read-only

get_timeline_summary read-only

get_timeline_gaps read-only

get_used_media_report read-only

get_offline_media read-only

check_offline_media read-only

get_unused_media read-only

get_duplicate_media read-only

get_clip_properties read-only

get_clip_speed read-only

get_clip_at_position read-only

get_clip_at_playhead read-only

get_premiere_state read-only

get_version_info read-only

ping read-only

create_project writes

open_project writes

save_project writes

save_project_as writes

close_project writes

import_media writes

import_folder writes

import_image_sequence writes

import_fcp_xml writes

import_sequences_from_project writes

import_sequences writes

create_bin writes

rename_bin writes

delete_bin destructive

create_smart_bin writes

move_item_to_bin writes

move_items_to_bin writes

rename_project_item writes

rename_clip writes

delete_project_item destructive

delete_multiple_project_items destructive

create_subclip writes

refresh_media writes

relink_media writes

replace_clip_media writes

get_metadata read-only

set_metadata writes

get_xmp_metadata read-only

set_xmp_metadata writes

get_footage_interpretation read-only

set_footage_interpretation writes

set_color_label writes

get_color_label read-only

set_project_panel_metadata writes

create_sequence writes

create_sequence_from_preset writes

create_sequence_from_clips writes

duplicate_sequence writes

delete_sequence destructive

close_sequence writes

set_active_sequence writes

get_sequence_structure read-only

get_sequence_count read-only

set_sequence_settings writes

set_sequence_frame_rate writes

set_sequence_resolution writes

set_sequence_audio_settings writes

set_sequence_pixel_aspect_ratio writes

set_sequence_field_type writes

add_track writes

add_tracks writes

delete_track destructive

rename_track writes

lock_track writes

toggle_track_visibility writes

set_target_track writes

set_all_tracks_targeted writes

get_track_info read-only

get_target_tracks read-only

get_sequence_in_out_points read-only

add_to_timeline writes

add_to_timeline_batch writes

insert_from_source writes

overwrite_from_source writes

overwrite_clip writes

remove_from_timeline destructive

remove_selected_clips destructive

ripple_delete destructive

move_clip writes

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 Desktop

Claude Code

Codex

GitHub Copilot in VS CodePartial support

CursorPartial support

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Hevy MCP 77 · B

Manage your Hevy workout data from AI assistants via MCP.

★ 529 · Tools 26 Compare with this →

Firecrawl MCP Server 75 · B

Firecrawl's official MCP server for web search, scraping, and structured extraction for AI agents

★ 7.7k · Tools 11 Compare with this →

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 670 · Tools 11 Compare with this →

Compartment 75 · B

Encrypted, fully offline long-term memory for AI agents

★ 579 · Tools 14 Compare with this →

Compare with other MCP servers

Source revision b866e6486749 Data synced 2026-11-02 Read the FMRS scoring method