Premiere Pro
The Premiere Pro MCP server works with projects and media, bins, sequences, timeline edits, markers, effects and keyframes, color, audio, graphics/captions, transcripts, metadata and export.
What this implementation covers
Project and media; sequences/settings; timeline clips/tracks; markers; effects, transitions and keyframes; color and audio; graphics/captions/transcripts; metadata; export and application events.
For feature-level detail and evidence, see the Capability Atlas.
Connection and requirements
How it reaches the app
A local WebSocket server connects to the MCP Bridge UXP panel inside Premiere Pro. Premiere UXP initiates the connection to the local server.
What you need
Premiere Pro 25.6+; Node.js 18+; macOS or Windows; UXP Developer Tool to load the plugin until the package provides a published installation route.
Package: adobe-mcp-premiere. Add it as a local stdio MCP server using CLI & client configuration.
API and content conventions
The package guide says not yet tested against a real Premiere Pro session. Read its security, version-specific API limitations, connection steps and “What is not certain yet” section before production use.
Discover the running package’s exact tool names and JSON input schemas through MCP tools/list. If the server provides help, use it to inspect a tool or category. Schemas from a different package version may not match.
Target and units: Times are seconds. Clips use track and index values returned by list_clips; indexes shift after edits. Project item IDs come from list_project_items. Output paths must be home-folder or PREMIERE_ALLOWED_DIRS; overwrites require explicit option.
CLI and configuration
This package is launched as a persistent MCP process, not as a conventional one-shot CLI. Relevant settings documented by the package include:
PREMIERE_WS_PORT, BRIDGE_TOKEN or PREMIERE_BRIDGE_TOKEN, PREMIERE_ALLOWED_DIRS, PREMIERE_SCRIPT_TIMEOUT_MS, PREMIERE_CONNECT_WAIT_MS.
Variable names and defaults are package-specific; consult the package README before changing them. File-operation permissions and bridge tokens should be configured in the client’s environment, not embedded in prompts or checked into source.
claude mcp add premiere -- npx -y adobe-mcp-premiereFor client-neutral JSON configuration and source-checkout commands, see CLI & configuration.
Full reference
The repository README is maintained alongside this implementation and covers exact setup, tool families, package-specific behavior, limitations, security and development status.