Premiere Pro MCP Server — Claude Code MCP server: setup guide
Controls projects, sequences, and timeline edits in Adobe Premiere Pro directly from your MCP client. Useful for scripted editing workflows.
claude mcp add --env PREMIERE_WS_PORT=<PREMIERE_WS_PORT> --env BRIDGE_TOKEN=<BRIDGE_TOKEN> --env PREMIERE_ALLOWED_DIRS=<PREMIERE_ALLOWED_DIRS> --env PREMIERE_SCRIPT_TIMEOUT_MS=<PREMIERE_SCRIPT_TIMEOUT_MS> --env PREMIERE_CONNECT_WAIT_MS=<PREMIERE_CONNECT_WAIT_MS> --transport stdio premiere -- npx -y adobe-mcp-premiereWhat Premiere Pro MCP Server does
This server connects AI assistants to Premiere Pro using an internal UXP plugin. Premiere lacks typical external control like COM or AppleScript dictionaries, so Adobe relies on UXP panels. The MCP process acts as a local WebSocket server on 127.0.0.1:3011. Inside the editor, the MCP Bridge panel initiates the connection to listen for editing commands.
Setup requires Premiere Pro 25.6 or newer, Node.js 18, and Adobe's UXP Developer Tool to load the bridge panel. All helper scripts were verified against mock DOM structures from Adobe API documentation rather than live Premiere sessions. Clip indexes also shift after timeline cuts, so expect to query clip lists again during multi-step edits.
What it helps with
- import media files directly into organized bins
- split timeline clips and position playheads by seconds
- apply video effects and transitions to active tracks
- relink offline footage across the open project
Example prompts for the agent
- Run
premiere_statusto see if the bridge plugin is connected - Insert a chapter marker at second 12 on the current sequence
- Create a bin named B-Roll and import footage from my home folder
How to install Premiere Pro MCP Server
Platform CLI
claude mcp add --env PREMIERE_WS_PORT=<PREMIERE_WS_PORT> --env BRIDGE_TOKEN=<BRIDGE_TOKEN> --env PREMIERE_ALLOWED_DIRS=<PREMIERE_ALLOWED_DIRS> --env PREMIERE_SCRIPT_TIMEOUT_MS=<PREMIERE_SCRIPT_TIMEOUT_MS> --env PREMIERE_CONNECT_WAIT_MS=<PREMIERE_CONNECT_WAIT_MS> --transport stdio premiere -- npx -y adobe-mcp-premiereReplace <…> with your own values
Platform CLI
codex mcp add premiere --env PREMIERE_WS_PORT=<PREMIERE_WS_PORT> --env BRIDGE_TOKEN=<BRIDGE_TOKEN> --env PREMIERE_ALLOWED_DIRS=<PREMIERE_ALLOWED_DIRS> --env PREMIERE_SCRIPT_TIMEOUT_MS=<PREMIERE_SCRIPT_TIMEOUT_MS> --env PREMIERE_CONNECT_WAIT_MS=<PREMIERE_CONNECT_WAIT_MS> -- npx -y adobe-mcp-premiereReplace <…> with your own values
Config file
{
"mcpServers": {
"premiere": {
"command": "npx",
"args": [
"-y",
"adobe-mcp-premiere"
],
"env": {
"PREMIERE_WS_PORT": "<PREMIERE_WS_PORT>",
"BRIDGE_TOKEN": "<BRIDGE_TOKEN>",
"PREMIERE_ALLOWED_DIRS": "<PREMIERE_ALLOWED_DIRS>",
"PREMIERE_SCRIPT_TIMEOUT_MS": "<PREMIERE_SCRIPT_TIMEOUT_MS>",
"PREMIERE_CONNECT_WAIT_MS": "<PREMIERE_CONNECT_WAIT_MS>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"premiere": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"adobe-mcp-premiere"
],
"env": {
"PREMIERE_WS_PORT": "<PREMIERE_WS_PORT>",
"BRIDGE_TOKEN": "<BRIDGE_TOKEN>",
"PREMIERE_ALLOWED_DIRS": "<PREMIERE_ALLOWED_DIRS>",
"PREMIERE_SCRIPT_TIMEOUT_MS": "<PREMIERE_SCRIPT_TIMEOUT_MS>",
"PREMIERE_CONNECT_WAIT_MS": "<PREMIERE_CONNECT_WAIT_MS>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e PREMIERE_WS_PORT=<PREMIERE_WS_PORT> -e BRIDGE_TOKEN=<BRIDGE_TOKEN> -e PREMIERE_ALLOWED_DIRS=<PREMIERE_ALLOWED_DIRS> -e PREMIERE_SCRIPT_TIMEOUT_MS=<PREMIERE_SCRIPT_TIMEOUT_MS> -e PREMIERE_CONNECT_WAIT_MS=<PREMIERE_CONNECT_WAIT_MS> premiere npx -y adobe-mcp-premiereReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Premiere Pro MCP Server
How to install Premiere Pro MCP Server in Claude Code?
Run claude mcp add adobe-mcp-premiere -e BRIDGE_TOKEN=<BRIDGE_TOKEN> -- npx -y adobe-mcp-premiere in your terminal. After that, load the plugin manifest via the UXP Developer Tool and click Connect in Premiere Pro.
What does Premiere Pro MCP Server do?
It exposes timeline manipulation, sequence settings, bin management, and project actions to an AI agent. Commands pass to Premiere Pro through an internal UXP panel connection.
Why does this setup require the UXP Developer Tool?
Adobe currently requires the developer utility to load unpublished UXP plugins. Premiere Pro has no standard system scripting interface, making the internal panel the only direct bridge.
