Cavi Premiere MCP
MCP server for Adobe Premiere Pro on macOS. It runs ExtendScript in Premiere Pro through an Adobe Bridge BridgeTalk relay, exposes the common Premiere Pro operations as 42 typed tools, and cuts a clip list into a new project with transitions and a ProRes 422 HQ master.
Try one cut
Cut three shots and a score into a new project with cross dissolves, and export the master. The stills below were exported by Premiere Pro from that project at 1.5, 3, 4.5 and 7.5 seconds.
The request is cut.json, the shots and score are in
examples/first-cut/media, and the measured answer is
results.json: a 9 second ProRes 422 HQ master, 1280 by 720 at 24 fps,
216 frames counted by ffprobe. Reproduce the cut with one command.
Install
Requires macOS, Premiere Pro 2026 or later, Adobe Bridge 2026 or later (the script relay), FFmpeg
(ffprobe) and Python 3.15 or later with uv. You supply your own licensed Adobe
applications.
uv tool install cavi-premiere-mcp
Upgrade with uv tool upgrade cavi-premiere-mcp. To work from a checkout instead, see
CONTRIBUTING.md.
Install the relay script into Bridge and approve it once in Bridge Settings > Startup Scripts; the steps are in Set up the Bridge relay.
Quickstart
Register the stdio server with your MCP client:
{"mcpServers": {"premiere": {"command": "cavi-premiere-mcp"}}}
If your client does not inherit your shell's PATH, use the absolute path that
command -v cavi-premiere-mcp prints. Then ask your agent to:
- Call
premiere_statusto see the installed applications and the relay state. - Call
premiere_bridge_install, restart Bridge and approve the relay, once. - Call
premiere_cutwith the request from cut.json, its media paths made absolute, thenpremiere_inspectto read the new project back.
The quickstart shows each step with its result.
Paths are absolute, times are seconds, tracks are 0-based, and sequence defaults to the active sequence.
What it does
| Tool | What it does |
|---|---|
premiere_status |
Installed Premiere Pro, Adobe Bridge and Media Encoder, relay state and mailbox. |
premiere_bridge_install |
Copies the relay startup script into Adobe Bridge. |
premiere_script |
Runs a .jsx file in Premiere Pro. |
premiere_cut |
Cuts a clip list into a new project and exports a ProRes 422 HQ master. |
premiere_project |
Opens, creates, saves or closes a project. |
premiere_inspect |
Bins, project items, sequences, tracks, clips, transitions and markers. |
premiere_transitions |
Lists the video and audio transitions Premiere offers. |
premiere_presets |
Lists export and sequence presets. |
premiere_effects |
Lists the video and audio effects Premiere offers. |
premiere_find |
Finds project items and placed clips by name or path. |
premiere_import |
Imports files into a bin. |
premiere_items |
Renames, moves, labels, subclips, interprets, proxies or deletes a project item. |
premiere_bins |
Creates, renames, deletes bins and moves items into them. |
premiere_media_replace |
Points a project item at a new file or refreshes it. |
premiere_sequence_new |
Creates an empty sequence. |
premiere_sequence_set |
Changes settings, in/out points, nests, duplicates, renames or deletes a sequence. |
premiere_tracks |
Adds tracks and sets mute, lock and target state. |
premiere_clip_place |
Places a project item on a track. |
premiere_clip_edit |
Trims, moves, enables, renames, links or removes a placed clip. |
premiere_clip_copy |
Places another copy of a clip. |
premiere_clip_slip |
Shows a different part of a clip's source in the same place. |
premiere_clip_speed |
Sets a clip's speed or the duration it fills. |
premiere_clip_fit |
Scales a clip to fit or fill the frame. |
premiere_clip_props |
Sets Motion, Opacity and Volume, static or keyframed. |
premiere_fade |
Fades a clip in and out. |
premiere_color |
Basic Lumetri Color correction. |
premiere_effect_add |
Adds an effect to a clip. |
premiere_effect_set |
Sets or lists component parameters. |
premiere_transition_add |
Adds a transition to a clip edge. |
premiere_razor |
Splits clips at times. |
premiere_gaps |
Lists or closes empty gaps. |
premiere_range_remove |
Cuts a time range out of every unlocked track. |
premiere_scene_detect |
Finds hard cuts in a clip's media and optionally splits or marks them. |
premiere_markers_add |
Adds sequence markers or a beat grid. |
premiere_markers_edit |
Lists, updates or deletes sequence markers. |
premiere_mogrt_add |
Places a Motion Graphics template and sets its text. |
premiere_captions |
Imports an .srt as a caption track. |
premiere_auto_reframe |
Makes a new sequence at another aspect ratio. |
premiere_frame_export |
Exports PNG stills of a sequence. |
premiere_export |
Exports a sequence with a preset. |
premiere_encode |
Queues a sequence in Media Encoder. |
premiere_interchange |
Exports FCP XML, AAF or OMF, or imports an FCP XML. |
Every tool is a script in src/cavi_premiere_mcp/jsx run through the relay with CAVI_ARGS, and answers
the JSON report the script writes. The tools reference
has each tool's parameters, defaults and results.
Documentation
The documentation source is in docs/premiere-mcp/source:
- Overview, installation and quickstart
- Guides: Bridge relay setup, a first edit, cutting from a clip list, export and encode and troubleshooting
- Reference: tools, results and errors, configuration and Premiere Pro behavior
- Security model and version and support
Configuration
| Variable | Meaning |
|---|---|
CAVI_PREMIERE_APP |
The Premiere Pro .app to use. |
CAVI_BRIDGE_APP |
The Adobe Bridge .app to use. |
CAVI_MEDIA_ENCODER_APP |
The Media Encoder .app to use. |
Without an override the newest installed version under /Applications is used. An override that names
another application is refused.
Security
The server speaks MCP over stdio, sends no telemetry and uses no accounts. premiere_script runs a
caller-chosen .jsx file in Premiere Pro, and any local process that can write the relay mailbox can run
ExtendScript in Adobe applications. See the
security model and SECURITY.md.
Tests
uv sync --locked --dev
uv run --locked ruff check .
uv run --locked pytest -q
npm install
npm run eval:protocol
npm run eval:core
The unit tests need no Adobe application; tests that need FFmpeg or Node.js skip without them. The
tests also fail when the README or the tools reference and the registered tools differ. The two evals run
the server over stdio with MCP Eval: eval:protocol checks the MCP contract of the catalog, and
eval:core also plays the input checks that happen before Premiere Pro is touched. They use no Adobe
application, so they do not exercise the tools inside Premiere Pro.
Contributing
See CONTRIBUTING.md for setup, checks and the rules for changes. This project follows the Code of Conduct.
License
MIT. See LICENSE.
Trademarks
Adobe, Premiere Pro, After Effects, Adobe Bridge and Media Encoder are either registered trademarks or trademarks of Adobe in the United States and/or other countries. This project is not affiliated with, endorsed by, or sponsored by Adobe. It does not include or redistribute Adobe software, templates or presets; you supply your own licensed applications.
Metadata
Release files for cavi-premiere-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cavi_premiere_mcp-0.1.0.tar.gz | 67.5 kB | With provenance | Details for cavi_premiere_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cavi_premiere_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for cavi_premiere_mcp-0.1.0-py3-none-any.whl |
Total release size: 138.0 kB
Release files / cavi_premiere_mcp-0.1.0.tar.gz
| Download URL | cavi_premiere_mcp-0.1.0.tar.gz |
|---|---|
| Size | 67.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e50de3684360adb184a6ad37fd7234a152821acc159dcf27d7bc4a5382dc34bc
|
|
BLAKE2b-256 checksum How to use checksums |
592d5ac7d4aa341fbc59616b5653fe58cb27f6579520f044bf4a33520d4990e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logRelease files / cavi_premiere_mcp-0.1.0-py3-none-any.whl
| Download URL | cavi_premiere_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 70.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6fd9a337c185706e7233baef1ba05f0ca1a24186be31fe6b5bce2569d2df92bf
|
|
BLAKE2b-256 checksum How to use checksums |
87aa2945178f1357e5ecd70e0378d79c6bcf28015317bfdaaf3861226bf1aaba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logSecurity for cavi-premiere-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for cavi_premiere_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.