premiere-claude-bridge
AI assistant editor for Premiere Pro and DaVinci Resolve. Open-source MCP server for Claude Code and Codex: logs footage, transcribes, builds rough cuts, makes subtitles, checks colour and loudness.
Install / Use
claude mcp add koptsev63 -- npx -y github:koptsev63/premiere-claude-bridgeIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
Content & MediaSupported Platforms
Tags
Our assessment of premiere-claude-bridge
premiere-claude-bridge scores 83/100 on our quality scale, 895th of 1,148 Content & Media skills we index.
Its MCP Server is 36 KB long, well organised into 40 sections with 10 code examples: a thorough specification that gives an agent plenty to work with.
It has 3 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated yesterday, so premiere-claude-bridge is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-11-22. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
premiere-claude-bridge compared with similar skills
All 4 of these similar skills score higher than premiere-claude-bridge; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| premiere-claude-bridge (this skill)by koptsev63 | 83 | 3 | 1d ago | MCP Server |
| Agent-Reachby Panniantong | 100 | 114.0k | today | CLAUDE.md |
| hyperframesby heygen-com | 100 | 88.2k | today | CLAUDE.md |
| rufloby ruvnet | 100 | 82.3k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 80.5k | today | CLAUDE.md |
Frequently asked questions
- How do I install premiere-claude-bridge?
- Run
claude mcp add koptsev63 -- npx -y github:koptsev63/premiere-claude-bridge. The install tabs above show the steps for each supported agent. - Which AI agents does premiere-claude-bridge work with?
- It is written for Claude Code, Claude Desktop and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
- Is premiere-claude-bridge safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is premiere-claude-bridge still maintained?
- The repository was last updated yesterday, so premiere-claude-bridge is actively maintained.
Skill content
View source on GitHubAI assistant editor for Premiere Pro and DaVinci Resolve
premiere-claude-bridge is a free, open-source MCP server that lets Claude Code or Codex do the assistant editor's work inside your own project. You ask in plain language. It logs the footage, transcribes the speech, lays out a rough cut on your timeline and checks the result before you ship it.

Recorded live in Premiere Pro and replayed at speed: 41 tool calls in three minutes. Claude imports 16 shots and a music track, lays the shots on the beat as colour-coded blocks, mixes the sound, exports and measures the result. Two gates fail: loudness is at -18 LUFS and two cuts miss the hit by under three frames. It fixes both in the timeline and measures again until every gate passes. Then it grades with Lumetri, keyframes a push-in and builds a 9:16 reel with captions and a 15-second teaser. The Premiere window is the raw recording; the log panel on the left and the step captions were added in the edit. Watch the mp4 with sound.
Install in one sentence
Open Claude Code (the Code tab of the Claude desktop app works) and send it this:
Install premiere-claude-bridge from github.com/koptsev63/premiere-claude-bridge following its README, and take me to the green "Connected" label in Premiere.
Claude clones the repo, sets everything up and tells you when to restart Premiere. Then:
- In Premiere open Window → Extensions → Claude Bridge. The panel should say "Connected to Claude".
- Start a new chat and ask: "Check the connection to Premiere."
- Keep that Claude session open while you edit.
On DaVinci Resolve Studio there is no panel. Set Preferences → System → General → External scripting using to Local, restart Resolve, and ask Claude to set the project up for Resolve.
You need Premiere Pro 2024 or newer, or DaVinci Resolve Studio, and a Claude or Codex subscription. Tested on macOS. Windows has install steps but nobody has confirmed them yet. Prefer to do it by hand? See Manual install.
For editors (Russian-speaking users)
How to install. Open Claude (the app, Code tab) and send it this phrase: "Install the Premiere bridge from github.com/koptsev63/premiere-claude-bridge and take me to the green Connected label in Premiere." Claude does the rest and tells you when to restart Premiere.
How to work. In Premiere open Window → Extensions → Claude Bridge. The panel should be green. Talk to Claude in plain words: "build a 1080 by 1920 sequence from this file", "put markers on the pauses", "open all the podcast sequences in tabs".
How to update. Tell Claude: "update the bridge". Then close and reopen Claude, and in Premiere close and reopen the panel. When a new version is out, Claude says so when it checks the connection.
If Premiere does not respond. Most often Premiere has a dialog open that is waiting for a click. Ask Claude: "Is Premiere waiting for a click?" It will name the window and the button.
If a video arrives with no picture. Clips from YouTube are often in a format that Premiere opens without an image. Just ask Claude to import the file: the bridge checks it beforehand and makes a working copy if needed.
Help train the assistant. The panel has a checkbox "Help train the assistant", on by default since version 0.8.3. The bridge sends an anonymized outline of the edit: where the cuts are, how many takes were shot, shot lengths. No video, no audio, no names. Only work done after the bridge update is sent. If you do not want this, uncheck the box or tell Claude "do not send the journal". A project under NDA can be excluded: the checkbox "Do not send this project" or the phrase "do not send this project" to Claude. If you turn off the main checkbox, everything already sent is deleted. Details and the privacy policy: DATA.md.
Editors' chat. Questions, bugs, wishes, techniques: t.me/+Fw5nSiqUkCswNjBi
What you can ask it to do
Sort the footage
- Watch a whole folder of rushes and write a log: what is in the shot, where the motion and the sound are, which clips are shaky or tilted. You get one page with a frame strip per clip.
- Transcribe speech offline, in Russian, English, Hungarian and other languages, then flag the words it probably misheard.
- Find material by words: a character's lines, a topic, "the long monologue at night".
Build the cut
- Put takes on the timeline in order and mark the story beats.
- Cut out pauses and dead air.
- Pick the strongest moments of a long recording for a short version.
- Build two contrasting rough cuts from the same material so you choose.
- Make variants of a cut you built by hand: drop a scene, insert a block, keep every other frame where it was.
Sound and subtitles
- Duck music under speech and level the takes against each other.
- Deliver subtitles as SRT and burned in.
Colour and hand-off to the colourist
- Match camera, AI-generated and drone shots to one colour point, shot by shot, then bake three looks as LUTs and render them with ffmpeg.
- Pull a "kolbasa" for grading from an editor's Resolve
.drt: every shot relinked to the camera originals, grade removed, ProRes 422 HQ. It stops before the render if one shot out of eighty does not match the editor's cut.
Check before delivery
- Refuse a grade with blown highlights or red skin, and a grade nobody can see.
- Refuse a file with wrong proportions, shaky edges or no sound.
Follow your hands. Move the cuts, retype a caption, save the project. It reads your saved .prproj and works from your version from then on.
It has no taste. Decisions stay with you; it takes the logging, sorting and checking.
What an editor said
"Everything installed by your instruction with no problems. The only snag was setting up the first connection."
"So far I have used the assistant only for basic organisation of files on the timeline, like putting takes in chronological order and cutting the empty phases. It handled that very well, it is all quite intuitive."
Andrey, film editor, October 2026
The snag he hit is now step 2 above.
New in 0.4: the wrong shot nobody sees
A real Sunday on a festival teaser. The editor cut it in Resolve on proxies and sent a .drt. The colourist needed the same cut on the 4K S-Log3 camera originals. The import looked clean and the length matched to the frame. One shot of 79 was still wrong, and it went out three times:
- Resolve put a crowd shot where the editor had an orbit around the hero.
- The "fix" trusted the number in the
.drtand put in a third shot. - The editor sent the timecode, and only then was the shot right.
A contact sheet with a frame every seven seconds cannot see a three-second shot. So core/drt_audit.py reads the cut twice, once from the .drt and once from what the NLE actually laid down, and compares them clip by clip. If they disagree, it does not render. It prints both readings and asks you for the editor's timecode. Neither file is the truth. The editor is. A clip the editor played backwards or retimed is read through Resolve's speed map, not its In field: a reverse goes into the pull as the forward source piece with a note to flip it back, any other speed change stops for the editor's timecode.
Same release: core/shotmatch.py pulls camera, AI and drone shots to one colour point and bakes the result into LUTs, about 60 times faster than grading every frame in Python. Details in CHANGELOG.
Demo
The clip at the top of this page is one session from an empty project to a measured export. A shorter one, with no cuts: a vertical reel assembled from one request in 23 seconds.

One request in Claude, and the bridge imports the clips, builds the vertical sequence, lays the shots on the timeline and adds markers and captions. Watch the mp4.
The same kind of session as text:
You: "Open Premiere. Import all .MTS from ~/Desktop/Footage/.
Create a 1080p25 sequence called 'Rough'. Place clips
00118 (1-6s), 00149 (4-9s), 00130 (1-5s) on V1 in order.
Add markers at every emotional beat per Murch's hierarchy."
Claude: ✓ Imported 108 clips into bin '01_Source_MTS'
✓ Created Rough - 1920x1080, 25fps, 3 V / 6 A tracks
✓ Placed 3 clips on V1, total 14 sec
✓ Marked 5 emotional beats: HOOK @0s, COMEDY @5s,
PIT @8s, BREATH @11s, PAYOFF @13s
→ Real output from this exact prompt. See examples/grave-stakes-teaser/cutlist_v3.json for the full 12-clip cutlist that built the case-study teaser.
How this compares to other Premiere and Resolve MCP servers
There are about fifteen Premiere MCP servers on GitHub now, and several for Resolve. The big ones are good at something this project is not, so here is the honest split (checked October 2026).
Where the others are ahead
- Typed timeline tools. hetpatel-11/Adobe_Premiere_Pro_MCP and leancoderkavy/premiere-pro-mcp ship hundreds of typed tools for effects, keyframes, transitions and multicam. Here those go through
pr_eval_jsx. - Install. They have npm packages and installers. This repo is a clone and a symlink.
- UXP. Both have a UXP preview. This panel is CEP only.
- Resolve depth. samuelgursky/davinci-resolve-mcp covers Fusion, Fairlight and the free edition. This project needs Resolve Studio and is tested on macOS.
What this project does that their READMEs do not mention
| | |
|---|---|
| Your edits come back | Reads the saved .prproj and conforms every later render to what you changed by hand |
| Gates that refuse | Colour, loudness and delivery checks raise an error instead of shipping a bad file |
| Work before the timeline | Auto-log of raw footage, offline transcript, dead-air removal, two rough-cut variants, subtitles |
| An editing method | Walter Murch's Rule of Six as decision rules in skills/film-editing/SKILL.md |
| One brain, two editors | The same cut list goes to Premiere or Resolve |
| Small surface | 35 tools, one of them the escape hatch pr_eval_jsx: a few dozen, not hundreds, so the model does not need a tool search to find its way |
If you need an agent that can reach every button in Premiere, pick one of the big servers. If you want an assistant editor for documentary material that checks its own output and follows your manual changes, this one is for you.
Why I built this
I'm a film director (festival shorts, currently developing two features in screenplay labs - Doukhobors in TFL Next, Grave Stakes in Cinéfondation). I monkey with Adobe Premiere all the time, and I burn 4-6 hours per teaser on the same boring assistant-editor work: watching all the dailies, writing notes in Excel, dragging selects to a timeline, trimming, re-timing.
I tried Adobe's own AI tools. Their official Creative Cloud connector advertises "Premiere capabilities" but the actual surface is four cloud video tools that have nothing to do with the desktop app. The Adobe docs themselves say: for trim by timestamp, use Adobe Premiere. So I made the thing that act
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
114.0kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
hyperframes
88.2kAI video you can actually edit. HyperFrames is a free, open-source AI video editor. Describe any video and get a real project you can change down to the frame.
ruflo
82.3k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
80.5kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
