Premiere Claude Bridge

What Premiere Claude Bridge MCP server does

Premiere Claude Bridge MCP server links an MCP-compatible agent with an active video-editing project. Its primary targets are Adobe Premiere Pro 2024 or newer and DaVinci Resolve Studio. The repository describes an assistant-editor workflow for logging footage, transcribing speech, assembling rough cuts, creating subtitles, and checking delivery results, while leaving editorial decisions with the human editor.

The bridge is intended for work inside a project rather than isolated media analysis. It can inspect saved Premiere project state, follow later manual changes, and help organize footage or timeline material. The repository also describes offline transcription, dead-air removal, rough-cut variants, subtitle delivery as SRT or burned-in captions, and checks for issues such as incorrect proportions, missing sound, blown highlights, or red skin.

How it works

An MCP client sends natural-language requests to the bridge. For Premiere, the connection is completed through the Claude Bridge panel opened from Window → Extensions → Claude Bridge; the panel should report that it is connected. After starting a new chat, the user can ask the agent to check the Premiere connection and keep that session open during editing.

Resolve uses a different path. In DaVinci Resolve Studio, there is no bridge panel. External scripting must be set to Local under Preferences → System → General, followed by a Resolve restart. The same cut list can be directed toward Premiere or Resolve, according to the repository description.

Setup and configuration

The supported agent choices named by the project are Claude Code, the Code tab in the Claude desktop app, OpenAI Codex, or another MCP-compatible client. Premiere runs on macOS and Windows; the repository says the Resolve path was tested on macOS and that Windows installation had not yet been confirmed. A Claude or Codex subscription is also listed as a prerequisite.

Installation can be initiated from Claude Code by asking it to install the repository from GitHub and follow its README. The project also provides a manual-install path. For Premiere, confirm the panel connection before starting an editing chat. For Resolve, configure local external scripting before asking Claude to prepare the project.

Tools and capabilities

Premiere Claude Bridge MCP server exposes focused MCP tools for common project and timeline operations:

• pr_status checks bridge health, Premiere version, and active project information.
• pr_get_project_info lists bins and project items, including node IDs for reference.
• pr_get_active_sequence reports dimensions, frame rate, and track counts.
• pr_list_timeline returns track-by-track clip data, including in, out, start, end, and duration values.
• pr_get_selected reads the clips currently selected on the timeline.
• pr_get_playhead provides CTI control.
• pr_add_marker places a named marker with a comment at a specified time.
• pr_export_ame queues an export in Adobe Media Encoder using an .epr preset.
• pr_eval_jsx runs arbitrary ExtendScript as an escape hatch for operations not covered by dedicated tools.

Limitations and notes

The project is marked beta. It is not presented as a replacement for an editor's judgment: sub-frame timing, micro-expression nuance, and overall dramatic structure still require human direction. The repository positions the system as senior assistant-editor automation rather than a director's editor.

Premiere-specific typed tools for effects, keyframes, transitions, and multicam are not exposed as dedicated operations; those tasks go through pr_eval_jsx. Resolve support requires the paid Studio edition, and the documented Resolve testing is on macOS. The bridge uses a CEP panel for Premiere rather than a UXP panel.