Give AI full control over Adobe Premiere Pro
An MCP server that lets Claude, Windsurf, Cursor, and any MCP‑compatible AI directly edit timelines, apply effects, manage keyframes, and export — via 28 tool modules.
$ npm install -g premiere-pro-mcp
$ premiere-pro-mcp --install-cep
# AI prompt:
"Add the B-roll to V2, cross dissolve between clips,
color correct to match A-roll, export 1080p ProRes."
[premiere-pro-mcp] Registered 269 tools + 2 resources ✓269 tools across 28 modules
Everything the AI needs to edit
add_to_timelineapply_effectcolor_correctexport_sequenceadd_keyframecreate_sequenceimport_mediaripple_deleteroll_editapply_lutcapture_framestabilize_clipadd_to_timelineapply_effectcolor_correctexport_sequenceadd_keyframecreate_sequenceimport_mediaripple_deleteroll_editapply_lutcapture_framestabilize_clipadd_to_timelineapply_effectcolor_correctexport_sequenceadd_keyframecreate_sequenceimport_mediaripple_deleteroll_editapply_lutcapture_framestabilize_clipadd_to_timelineapply_effectcolor_correctexport_sequenceadd_keyframecreate_sequenceimport_mediaripple_deleteroll_editapply_lutcapture_framestabilize_clipexecute_extendscriptget_project_infoset_clip_propertiesauto_reframe_sequencecopy_effects_between_clipsset_keyframe_interpolationget_active_sequencecreate_caption_trackexport_aafsplit_clipset_workspaceget_premiere_stateexecute_extendscriptget_project_infoset_clip_propertiesauto_reframe_sequencecopy_effects_between_clipsset_keyframe_interpolationget_active_sequencecreate_caption_trackexport_aafsplit_clipset_workspaceget_premiere_stateexecute_extendscriptget_project_infoset_clip_propertiesauto_reframe_sequencecopy_effects_between_clipsset_keyframe_interpolationget_active_sequencecreate_caption_trackexport_aafsplit_clipset_workspaceget_premiere_stateexecute_extendscriptget_project_infoset_clip_propertiesauto_reframe_sequencecopy_effects_between_clipsset_keyframe_interpolationget_active_sequencecreate_caption_trackexport_aafsplit_clipset_workspaceget_premiere_stateCapabilities
Professional editing, fully automated
Every major Premiere Pro workflow is accessible via structured MCP tools with full error handling and result feedback.
Full Timeline Control
Insert, overwrite, trim, split, move, and ripple-delete clips. Roll, slide, and slip edits via QE DOM for professional-grade trimming.
Effects & Color Grading
Apply any effect by name, set Lumetri Color parameters, load LUTs, run Warp Stabilizer, and manage keyframes with bezier interpolation.
AI-Driven Workflows
Describe your edit in plain language. The AI plans the workflow, calls the right tools in order, and handles error recovery automatically.
Custom ExtendScript
Run any ExtendScript or QE DOM code on demand. The AI can write scripts to handle tasks beyond the built-in 269 tools.
Project & Media Management
Import media, manage bins, create sequences, reframe for social, consolidate projects, and batch-encode with Adobe Media Encoder.
File-Bridge Architecture
No network sockets. Commands flow via a shared temp directory — simple, reliable, and battle-tested across macOS and Windows.
Connect your LLM in 60 seconds
No local install required. Point any MCP-compatible AI client at our hosted endpoint and start editing Premiere Pro with AI immediately.
Install mcp-remote
One-time prerequisite — a tiny proxy that bridges HTTP/SSE to stdio.
$ npm install -g mcp-remoteAdd config to your client
Paste the JSON snippet below into your AI client's MCP config file.
Install the CEP panel
Run once on the machine with Premiere Pro to enable the file bridge.
$ premiere-pro-mcp --install-cepAdd to claude_desktop_config.json
Path: ~/Library/Application Support/Claude/
{
"mcpServers": {
"premiere-pro": {
"command": "npx",
"args": [
"mcp-remote",
"https://premiere-pro-mcp.fly.dev/mcp"
]
}
}
}https://premiere-pro-mcp.fly.dev/mcpRequires Node.js 18+ and the CEP panel installed on the machine running Premiere Pro.
How it works
File-bridge architecture
No network daemons, no native extensions. A battle-tested temp-directory IPC pattern that works reliably on macOS and Windows.
AI invokes a tool
Claude (or any MCP client) calls e.g. "add_to_timeline" with parameters.
ExtendScript is generated
The MCP server builds ES3-compatible ExtendScript with helper functions prepended.
Script written to temp dir
A .jsx command file is dropped into the shared temp directory (configurable via PREMIERE_TEMP_DIR).
CEP plugin executes it
The Premiere Pro panel polls for new .jsx files and runs them via CSInterface.evalScript().
Result returned as JSON
The CEP plugin writes a .json response; the MCP server polls for it and returns it to the AI.
Remote mode available
The server also ships an HTTP/SSE transport deployed at premiere-pro-mcp.fly.dev. Connect any MCP client via mcp-remote — the MCP endpoint and CEP plugin still communicate through the shared temp directory.
Get started
Two ways to connect
Local (stdio)
{
"mcpServers": {
"premiere-pro": {
"command": "premiere-pro-mcp"
}
}
}Works with Claude Desktop, Windsurf, Cursor, and any MCP client that supports stdio.
Remote (Fly.io)
{
"mcpServers": {
"premiere-pro": {
"command": "npx",
"args": [
"mcp-remote",
"https://premiere-pro-mcp.fly.dev/mcp"
]
}
}
}Note: the file bridge still requires the CEP plugin on the same machine or a shared volume.