mcp.film / Editing & Post / Adobe Premiere Pro MCP
Adobe Premiere Pro MCP
Drive Premiere Pro timelines, effects, and exports from your agent via a CEP bridge.
What it does
A 283-tool MCP server that controls Premiere Pro through a CEP extension bridge: import media, edit sequences, apply effects and transitions, and export, with context resources and guided prompts alongside the tools. Lets an agent do real NLE assembly inside the editor filmmakers already use, which Adobe's own connector does not offer.
Connect
claude mcp add premiere-pro -- premiere-pro-mcp
Local install: premiere-pro-mcp (after `npm install -g adobe-premiere-pro-mcp`, then `premiere-pro-mcp --install-cep` and `premiere-pro-mcp --doctor`; restart Premiere and start the bridge from Window > Extensions > MCP Bridge (CEP)). Node 20+, macOS or Windows, same machine as Premiere. Set PREMIERE_MCP_TOOLSET=full to list every tool instead of the search/invoke gateway.
Sample tools
import_mediaapply_effectadd_transitionget_sequencesget_active_sequenceexport_sequenceField notes
Packaged on npm as adobe-premiere-pro-mcp (MIT; 1.2.8 on 2 Sep 2026), so a global install plus `--install-cep` is the documented path and the client just runs the premiere-pro-mcp binary. Two things changed since August that bite: (1) tools/list now advertises only five tools by default — search_tools, get_tool_schema, invoke_tool, verify_premiere_connection, list_sequences — and the other 280 operations are reached through search_tools then invoke_tool; set PREMIERE_MCP_TOOLSET=full for a flat list (the README recommends that for Claude Code's native tool search). (2) Anonymous usage telemetry is ON by default — install id, OS, version, tool names and success/failure, not project names or media paths per the README; opt out with PREMIERE_MCP_TELEMETRY=0, DO_NOT_TRACK=1, or the checkbox in the CEP panel. The panel also nags about npm updates (PREMIERE_MCP_UPDATE_CHECK=0 to silence). Nothing connects until you open the CEP panel in Premiere and click Start Bridge; run `verify_premiere_connection` first. CEP is the supported bridge; UXP is explicitly experimental. Adobe DOES have an official MCP — the hosted 'Adobe for Creativity' connector, listed separately here — but its video surface is reformat/quick-cut class with no tool that opens or edits a Premiere project, so community bridges still own real editorial. This one: 607 stars, pushed 25 Sep 2026. Alternatives: leancoderkavy/premiere-pro-mcp (288 stars, MIT, pushed 25 Sep 2026) and ayushozha/AdobePremiereProMCP (106 stars, MIT, pushed 31 Aug 2026) — both clone-and-build.
Also in Editing & Post
First-party MCP server built into DaVinci Resolve Studio 21.1 — no third-party bridge.
Full AI control of DaVinci Resolve Studio — edit, grade, Fusion, and render via scripting.
Local MCP bridge into DaVinci Resolve that runs on the Free edition, not just Studio.
AI-native Mac timeline editor with a built-in local MCP server — closed source since v0.7.6.
Archived: a CapCut draft-builder whose repo is now read-only — use vectcut instead.
Assemble CapCut and Jianying draft projects from an agent over a local stdio MCP server.
Used in
Local Edit Bay · Archive To Trailer · Edit local footage without handing over the source library
Pairs well with
Quoted dubbing, subtitles, transcription and multi-voice audiobooks from one remote MCP; a human approves each price.
Official Deepgram server: Nova transcription, diarization, and audio intelligence.
Official hosted Airtable MCP: query, create, and update production-tracking bases.