MCP Bridge for Adobe Premiere Pro
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
MCP Bridge for Adobe Premiere Pro
Operate local Adobe Premiere Pro projects through MCP.
663 implemented tools — 112 advertised by default, all 663 reachable through call_tool — plus 21 context resources and 16 guided prompts for Codex, Claude Code, Claude Desktop, and other MCP clients. CEP is the supported production bridge; UXP remains experimental.
Start here: quit Premiere Pro, run npx -y premiere-mcp@latest setup, reopen Premiere and your AI app, then ask it to run verify_premiere_connection.
Using an AI agent to set this up? Point it at this repository; AGENTS.md has the exact steps.
Install | Claude Desktop | Other AI apps | Verify | Privacy Policy | Terms of Service | Security
⭐ Found this through an agent recommendation or a search? Every tool here verifies its own writes and refuses to report success it can't confirm — that honesty is the whole point. If it earned a place in your pipeline, a star on GitHub helps the next agent find it. Completely optional, and it changes nothing about how the tools behave.
Install
Needs Node.js 20+ and Adobe Premiere Pro (2020 or later, with Creative Cloud) on the same computer as your AI app. Quit Premiere Pro, then:
npx -y premiere-mcp@latest setupThat one command:
installs the signed Premiere bridge and UXP helper through Adobe's own plugin installer (the one Creative Cloud uses), so no developer mode and no panel to open: the bridge starts with Premiere and runs in the background;
adds this server to every AI app it finds (Claude Desktop, Claude Code, Codex, Cursor, VS Code), keeping your other servers and backing up each file it edits.
Add --dry-run to see the plan without changing anything, or --clients claude-code (also codex, cursor, vscode, claude-desktop) to set up one app. Then reopen Premiere Pro and your AI app.
Verify the install
npx -y premiere-mcp@latest doctorEvery line should read ok, including "Premiere is running with the bridge on". Then ask your AI app:
Run
verify_premiere_connection. Make no changes.
Claude Desktop
Each GitHub release also has premiere-mcp-<version>.mcpb: double-click it to add the server to Claude Desktop. On first launch it installs the signed bridge the same way setup does.
Other AI apps
setup covers the common ones. For any other MCP client, after npm install -g premiere-mcp:
{
"mcpServers": {
"premiere-pro": {
"command": "premiere-mcp",
"env": { "PREMIERE_TEMP_DIR": "/tmp/premiere-mcp-bridge" }
}
}
}The Codex and Claude Code plugins in this repository (codex plugin marketplace add ., /plugin marketplace add .) add the same server plus an editing skill; run setup once for the Premiere side.
Teammates without a terminal
Each release has Premiere-MCP-Installer-v<version>.zip (macOS): unzip, quit Premiere, double-click Install Premiere MCP.command. It installs the same signed plugins. The first time, macOS may say it cannot verify the developer: right-click the file, choose Open, then Open again.
Install from source
git clone https://github.com/skrfilms/premiere-mcp.git
cd premiere-mcp
npm install && npm run build
node dist/cli.js setup --clients claude-code # or codex, cursor, vscode, claude-desktopsetup installs the signed plugins from installer/. If that folder is missing (it is built by npm run release:installer, which needs the signing certificate), install the plugins from the release's installer zip and add --skip-plugins. setup --unsigned is the old route (hand-copied panel plus CEP developer mode) and clashes with the signed install; avoid it unless you know you need it.

Current CEP panel UI inside Premiere Pro, using the refreshed bridge controls and status layout.
Related MCP server: Premiere Pro MCP
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 (v1.5.0):
663MCP tools are implemented for AI-driven video editing.112are advertised by default (thecoreprofile) and all663stay reachable — advertising every tool costs roughly 113,600 tokens (~57% of a 200k context) before the conversation starts, published guidance puts tool-selection degradation past 30–50 tools, and VS Code / Copilot hard-errors above 128, so a curated menu is a context-cost decision rather than a capability one. Nothing is hidden silently and nothing is out of reach:find_toolsearches all663and reports a profile-hidden match asexposed: falsewith the reason,call_toolinvokes it anyway, andactivate_toolspromotes it into the advertised list mid-session (with atools/list_changednotification). SetPREMIERE_MCP_PROFILE=allto advertise everything up frontcoverage 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
local-compute tools that Premiere's scripting API cannot provide:
detect_silence(ffmpeg),transcribe_to_srt(local OpenAI Whisper speech-to-text),probe_media(ffprobe ground-truth metadata), andgenerate_scope(ffmpeg waveform / vectorscope / histogram / RGB-parade images) — each probes for its binary and returns install guidance instead of failing silentlya recovery boundary —
create_recovery_checkpoint,list_recovery_checkpoints,restore_recovery_checkpoint— snapshots a sequence before risky edits; the auto-checkpoint before destructive edits fails closed (the edit is refused if the snapshot cannot be taken)schema-on-demand:
find_tool(search) →get_tool_typings(exact signature) →call_tool(invoke) reaches the whole catalogue through three tool definitions instead of 663, andactivate_tools/deactivate_toolsgrow or shrink the advertised list at runtime while reporting the measured context cost of the change. The separation between advertised and reachable stops dead at an authority boundary:call_toolrefuses to route pastPREMIERE_MCP_PROFILE=read-only, an explicitPREMIERE_MCP_TOOLSallowlist, or aPREMIERE_MCP_EXCLUDEveto, and names the setting that refused it.tools/listalso supports cursor pagination, off unlessPREMIERE_MCP_PAGE_SIZEis set — paging by default would silently truncate the list for any client that ignoresnextCursortool profiles (
PREMIERE_MCP_PROFILE=core|all|read-only|audio|color, or an explicitPREMIERE_MCP_TOOLSallowlist) size the menu to the client's tool budget.core(112) is the default and is deliberately coherent rather than minimal — it includesset_effect_propertyalongsideapply_effect,add_keyframealongsidebake_keyframe_ease, andundo/redo, because a default that forces a profile switch on the second call is not a default
Most recent completed local live validation:
663tools are implemented and112are advertised under the default profile (all 663 reachable);get_capabilitiesreports the active profile, local installation, and optional live connection state, whileverify_premiere_connectionis the canonical read-only bridge and host readiness check0known parked or placeholder tools are advertisedimport_ae_compsis intentionally not advertised because Premiere returnedfalsefor real.aepfixtures in this environment and a generic.aepimport 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 & Whiteeffect 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_demoassemble_product_spotbuild_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 skrfilms/premiere-mcp --skill premiere-mcpOr install directly from the skill path:
npx skills add https://github.com/skrfilms/premiere-mcp/tree/main/skills/premiere-mcpThe 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
QUICKSTART.md covers Windows, client-specific configuration and diagnostics. The short version is Install: setup, reopen Premiere and the AI app, doctor, then verify_premiere_connection.
The bridge folder both sides use is /tmp/premiere-mcp-bridge (Windows: %TEMP%\premiere-mcp-bridge), or the folder saved in the bridge's status panel. Set PREMIERE_TEMP_DIR only to change it, and then on both sides.
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. npm run test:workflows runs whole editing jobs end to end against the scratch project.
How the Bridge Works
+-----------+ +-----------+ +-----------+
| Client | MCP | Node.js | Files | CEP Panel |
| (Codex+) |<------>| MCP Server|<------>| (Premiere)|
+-----------+ +-----------+ +-----------+
|
v
+-----------+
| Premiere |
| DOM / QE |
+-----------+The client calls an MCP tool.
The Node server generates ExtendScript plus shared helpers.
The script is written into
/tmp/premiere-mcp-bridge.The CEP panel polls that directory and runs the script through
CSInterface.evalScript().The panel writes the result back to the response file.
The server returns structured JSON to the MCP client.
Tools
All 663 implemented 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
Tools | What they do |
| Read-only host readiness and local runtime capability checks. |
| Inspect the current project, media/bin inventory, and sequences. |
| Read the current timeline, its clips/tracks, and sequence settings. |
| Return deeper project, sequence, or clip snapshots for planning. |
| Locate project items by name or media path. |
| Summarize the edit, detect gaps, and report media in use. |
| Find missing, unused, or duplicated media before an edit or export. |
| Inspect clip framing, speed, and timeline position. |
| Read a broad host state, Premiere version, or bridge health. |
Projects, media, and bins
Tools | What they do |
| Project lifecycle and file operations. |
| Bring video, audio, stills, or image sequences into the project. |
| Import supported timeline interchange or sequences from another project. |
| Create and organize project-panel bins. |
| Organize and rename existing project items. |
| Remove project items explicitly. These are destructive operations. |
| Create source ranges, refresh media, relink missing files, or replace clip media. |
| Read and write project metadata and XMP fields. |
| Inspect or change footage frame-rate and pixel-aspect interpretation. |
| Label and annotate project-panel items. |
Sequences and tracks
Tools | What they do |
| Make an empty sequence from an installed |
| Derive a sequence from pre-imported media when the clip settings should define the sequence. |
| Copy a sequence; |
| Manage which sequence is open or active. |
| Snapshot a sequence (as a reserved-name clone) before a risky edit, list snapshots, and restore one. The auto-checkpoint before destructive edits fails closed — if the snapshot cannot be taken, the destructive edit is refused rather than run unprotected. |
| Inspect a sequence layout or count project sequences. |
| Change supported sequence settings. Verify results because Premiere can quantize or reject changes. |
| Adjust supported audio, pixel-aspect, and field settings. |
| Create, remove, and name audio/video tracks. Caption-track deletion returns an explicit unsupported result. |
| Control edit protection, visibility, and track targeting. |
| Inspect tracks, targeting, and sequence in/out ranges. |
Timeline editing and trim operations
Tools | What they do |
| Place one or many project clips with per-clip source ranges and link-audio control. Batch placement returns per-clip results. |
| Perform three-point insert or overwrite editing from the Source monitor. |
| Remove timeline clips. Ripple deletion closes the gap when the host supports it. |
| Reposition a clip in time or on another track. |
| Cut one clip or multiple tracks at a requested timeline point. |
| Adjust edit points and clip content timing. Structural QE edits are read back rather than trusted blindly. |
| Lift/extract a selected range or create/remove nests. |
| Duplicate, replace, enable, or freeze timeline material. |
| Change clip speed/duration. |
| Manage audio/video link relationships. |
| Revert or reapply recent Premiere operations. |
Effects, color, motion, and keyframes
Tools | What they do |
| Discover installed effects, applied effects, and their properties. |
| Add or remove visual/audio effect components. |
| Add a video effect and verify it by diffing the clip's components, reporting the |
| Apply or copy effect treatments across clips. |
| Change supported effect parameters, color values, and blend modes. |
| Apply basic correction, LUTs, or Warp Stabilizer. |
| List every installed Lumetri color preset, then apply one to a video clip. |
| Crop a clip or use an adjustment layer for shared treatment. |
| Set opacity, scale, rotation, and position with verified per-property output. |
| Address individual Motion transform values. |
| Create, inspect, and remove parameter keyframes. |
| Set interpolation or query a parameter value at a given time. |
| Animate a scalar parameter (opacity, scale, rotation, volume) along any of 30 Penner easings or a CSS cubic-bezier, baked as a dense run of value keyframes. Premiere exposes no way to read a keyframe's ease back, so the shape is baked into readable values and every written point is verified — a genuine eased move that cannot silently misland. |
Audio, transitions, and captions
Tools | What they do |
| Set clip gain, volume, or pan. |
| Build volume automation or a full ducking curve from supplied windows. |
| Mute a track or apply audio processing to one or many clips. |
| Analyze a local media file with ffmpeg and return silence ranges. It does not edit the timeline. |
| Transcribe a media file's speech to an |
| Discover installed transition names. |
| Add one or many transitions. Results distinguish verified changes from accepted-but-unverified host responses. |
| Create a caption track from an imported subtitle project item, such as an SRT. Pair with |
| Reports scripting-visible caption data and explicitly flags that Premiere's DOM often cannot read existing caption text. |
| Read, QC, and write |
| Full cue-level CRUD and bulk timing shifts on an |
Markers, selection, navigation, and playback
Tools | What they do |
| Create and manage timeline markers. |
| Work with markers on project items, clips, or sequences. |
| Set or inspect sequence in/out points and work area. |
| Inspect and navigate the CTI/playhead. |
| Inspect or create targeted timeline selections. |
| Broader selection controls. |
| Control Source monitor media and source in/out points. |
| Start or stop timeline and source playback. |
Delivery, interchange, and media management
Tools | What they do |
| Validate a delivery, discover readable user |
| Queue a sequence through Adobe Media Encoder using a real preset path or exact preset name. |
| Report queue-monitoring availability or start supported batch encoding. |
| Report the timeline's render-bar state (green rendered / yellow real-time / red drop-risk / empty), with timed segments, totals, and a rendered fraction. Reads the QE DOM and addresses the sequence by guid. Distinct from |
| Write a still image from a sequence at a given time. Formats verified against Premiere's QE exporters: png, jpg/jpeg, tiff/tif, dpx, tga/targa. Hands Premiere the path stem so no double extension is written, and verifies the file landed on disk before reporting the real path. |
| Export supported interchange formats. |
| Encode a source item/file or export a project representation. |
| Inspect, attach, or detach proxies. |
| Change offline status, refresh media, or apply frame-size scaling. |
| Consolidate duplicate items or prepare a transfer workflow. |
| Read ground-truth technical metadata from any file on disk with ffprobe — exact codec, pixel format, color space/range, bit depth, frame rate, sample rate, channel layout, duration — including files Premiere has not imported. Returns a distilled summary plus the full ffprobe JSON. |
| Render a signal scope (waveform, vectorscope, histogram, or RGB parade) from one frame to a PNG with ffmpeg, because Premiere's Lumetri scopes cannot be scripted or exported. Verifies the image was written before reporting success. |
Graphics, workflows, workspace, and advanced operations
Tools | What they do |
| Add a MOGRT and optionally populate supported text fields. |
| Inspect Motion Graphics components and graphics white luminance. |
| Create a complete demo sequence with generated assets, dissolves, and subtle animation. |
| Assemble real media into a directed product/brand edit with optional clip plans and MOGRT overlays. |
| Use Premiere-assisted reframing or scene-change detection where the host supports it. |
| Inspect and switch Premiere workspace layouts. |
| Generate utility media or manage ingest and scratch-disk behavior. |
| Advanced diagnostic and scripting operations. Use only with trusted inputs and explicit user intent. |
| Enumerate the callable API surface of any DOM object via ExtendScript's |
Project-file surgery (off by default)
A .prproj is a gzip'd XML document, so the server can read and edit a project on disk without Premiere running. That reaches state the scripting API does not expose — but it also means a bug corrupts a real cut, so the write side is opt-in and heavily guarded.
Tools | What they do |
| Read-only. Reports format version, byte size, SHA-256, a structural census of nodes and |
| Applies exact literal replacements to a copy of a project. Requires |
project_file_edit refuses rather than guesses, and each refusal returns a code:
never writes in place —
outputPathmust be a new file, and the source is re-hashed afterwards to prove it was untouchedrefuses if the target's realpath is open in Premiere; if the bridge is down and Premiere may be running, it refuses with
OPEN_STATE_UNKNOWNrather than assumingrefuses an unrecognised
PremiereData Versionruns a per-file container canary (gunzip → gzip must reproduce the input byte-for-byte) before editing
exactly-N matches or refuse — there is no replace-all, and every count is checked against the original document before any edit is applied
refuses a bare
&in a replacement (write&) and a raw</>unlessallowMarkupEditis setchecks the whole edited document for balanced angle brackets and valid entity references
requires the structural census to be unchanged unless
allowCensusChangeis set, and reports the diff either wayreports
premiereWillLoad: "unverified". XML validity is not acceptance; only opening the file proves that, so useopen_projectand read the result backdryRunreturns the full report and the census diff without writing anything
Both tools are excluded from the core profile, so neither is advertised by default and neither is ever invoked as part of another tool. Reach them with PREMIERE_MCP_PROFILE=all, an explicit PREMIERE_MCP_TOOLS allowlist, or call_tool. The env flag gates the write side specifically: it is enforced inside project_file_edit rather than by the profile, because call_tool deliberately routes past a cost-shaped profile and an opt-in that a router can reach past is not an opt-in.
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
Premiere scripting still does not expose every UI operation cleanly.
Professional title design still depends on real MOGRT assets or external graphics workflows.
get_render_queue_statusis 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.
The bridge is signed with this project's own certificate. Premiere accepts it without developer mode, but it is not Adobe Marketplace approval, and macOS asks once before running the teammate installer.
Troubleshooting
Run npx -y premiere-mcp@latest doctor first: each failing line names the problem and the fix.
"no heartbeat" / calls time out: Premiere is not running, or was not restarted after setup. The bridge starts with Premiere;
Window > Extensions > MCP Bridge (CEP)shows its status.The AI app does not list the tools: quit and reopen the app (it loads servers at start). In Claude Code, start a new session.
"Adobe's plugin installer was not found": install Creative Cloud and Premiere Pro, then run
setupagain.A call timed out but may have run: ask for
get_recent_callsbefore retrying an edit.Something else: open an issue with the
doctoroutput.
Developer Notes
Useful commands:
npm run build
npm test -- --runInBand
npm run setup:doctor
node scripts/live-tool-sweep.mjsSee:
QUICKSTART.mdfor the shortest install pathKNOWN_ISSUES.mdfor current limitsCONTRIBUTING.mdfor development workflow
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
AI video editor for agents and humans: timeline, captions, color, audio and generation as MCP tools.
AI video editor your agent can drive: plan scenes, edit a multi-track timeline, and render MP4s.
Transform video, audio and images, and generate media from prompts. FFmpeg, captions, models.
FFmpeg as a service for AI agents: typed video editing tools, async jobs, downloadable outputs.
Related MCP Servers
- AlicenseCqualityCmaintenanceOperates local Adobe Premiere Pro projects through MCP, exposing 284 tools for AI-driven video editing including timeline editing, effects, exports, and guided assembly workflows.28454 npmMIT
- AlicenseCqualityCmaintenanceGives an AI client local control over Adobe Premiere Pro, letting it inspect footage frame-by-frame to find the best moments, assemble and trim edits on the timeline, render animated title cards, review its own work, and export the finished video. Vision and editing tools run entirely on the user's own computer, with nothing sent to the publisher.289MIT
- AlicenseNot gradedqualityBmaintenanceEnables editing Adobe Premiere Pro projects and sequences from Claude Code through local pr_* tools, including media import, clip placement and properties, effects and LUT copying, frame/video export, and batched edit plans.MIT
- AlicenseAqualityBmaintenanceLets AI agents drive a running Adobe Premiere Pro (~440 verified operations). Works with every UI language Adobe ships and sees the frame: draws Object Masks on what it sees (a click for a person, a lasso for a face; ⊕/⊖, tracking) and places speed keyframes on the timeline by sight. A large skills library, built for Generative Extend, Generative Media, Object Mask, Enhance Speech.49796 npmApache 2.0