export const meta = { title: "Premiere Pro MCP: Connect an AI Assistant and Build an Editable Timeline", description: "Connect an AI assistant to Premiere Pro with pinned premiere-pro-mcp@1.29.0, then verify the bridge and build a three-clip timeline that reopens cleanly.", tldr: "Pin premiere-pro-mcp@1.29.0, install its CEP bridge, inspect capabilities, confirm the assistant can connect to Premiere, then test with a saved three-clip 24 fps timeline before using real projects.", slug: "premiere-pro-mcp-editable-timeline", publishedAt: "2026-11-07", readingTime: 11, thumbnail: "https://cdn.aspectlabs.dev/blog/premiere-pro-mcp-editable-timeline/cover-39961fbd0afe.png", authors: [ "bright" ], primaryTopic: "post-production", topics: [ "post-production" ], tags: [ "editing", "media-management" ], faq: [ { question: "Which Premiere Pro MCP package should I use for this workflow?", answer: "Use the independent premiere-pro-mcp project documented at premiere-pro-mcp.com, and pin the manual setup to premiere-pro-mcp@1.29.0. Pinning matters because another Premiere MCP package uses the same global command name, so an unpinned command can connect your client to a different implementation." }, { question: "Does downloading a ZXP file install the Premiere extension?", answer: "No. A ZXP file is only an extension package until you install it. For this workflow, use the documented command npx --yes premiere-pro-mcp@1.29.0 --install-cep rather than mixing in installation steps from another repository." }, { question: "What does the CEP compatibility bridge do?", answer: "The CEP compatibility bridge installs a local Premiere extension panel that lets the MCP server communicate with Premiere Pro. On our Mac, the installer enabled PlayerDebugMode, which allows unsigned CEP extensions in Premiere’s CEP host." }, { question: "How do I know Premiere is actually connected before editing a project?", answer: "Open Premiere, go to Window > Extensions > MCP for Adobe Premiere Pro, and confirm the panel shows Connector running. Then have your MCP client call get_capabilities to inspect the available tools, followed by verify_premiere_connection as a read-only connection test before making any project changes." }, { question: "Why use a three-clip timeline test first?", answer: "Use the test to check that your assistant can import clips, assemble a sequence, and save a project you can reopen. You should see a 24 fps non-drop-frame sequence starting at 00:00:00:00, three five-second clips on the timeline, sequence markers at 00:00:00:00, 00:00:05:00, and 00:00:10:00, stable media paths, and a clean save, close, and reopen." } ], draft: false } You can use an AI assistant to import three clips, assemble a Premiere timeline, and add markers that your team can inspect. The connector in this workflow is the independent `premiere-pro-mcp@1.29.0` package with its CEP compatibility bridge. Install the specific package, inspect the exposed capabilities, confirm the assistant can connect to Premiere with the connection tool, and try the workflow on sample media before using project media. For this workflow, use the [independent Premiere Pro MCP project](https://github.com/leancoderkavy/premiere-pro-mcp/) documented by the project site for `premiere-pro-mcp`. Pin the package version in your MCP config. That matters because another Premiere MCP package uses the same global command name, so an unpinned or copied install command can put you on the wrong implementation. This article uses the manual setup for `premiere-pro-mcp@1.29.0`: [Node.js 20.19 or newer](https://premiere-pro-mcp.com/docs/), the package’s CEP installer, its doctor command, and the exact MCP JSON for that version. We tested this connector on macOS 26.2 with Premiere Pro 26.5.2 and Node.js 25.8.1. We used its MCP tools to assemble three generated test clips, save the project, close it, and reopen it. Claude Desktop 4.4212.0 then inspected the connection and timeline. This verifies the connector operations and Claude’s inspection; we have not tested Claude planning the full assembly from a single prompt. ## Where this setup fits
The connector maintainer's three-clip demo
The connector maintainer's three-clip demo. The maintainer demonstrates an assembly in Premiere Pro 26.5. The request text is an editorial overlay, not captured AI chat. This is an external example, not our test or proof of every supported version. Reference video · Premiere Pro MCP maintainer
Premiere Pro MCP isn't a replacement for an editor, an assistant editor, or your team’s checks for media paths, sequence settings, and saved results. It gives an MCP-compatible AI assistant tools for inspecting and changing a local Premiere project. In a post workflow, we recommend using it for work you can describe precisely: importing known media, creating a named sequence, placing clips at specified time ranges, adding markers, and saving an editable project. That's different from asking an assistant to “make a good edit.” Ask for a smaller task that your team can check in Premiere: “Import these three files, create this sequence, place each clip for five seconds in this order, add review markers at the opening and each cut, then report the timeline positions and media paths.” That kind of request maps to real assistant-editor work. It also gives you something you can inspect in Premiere’s own UI. If the assistant creates an editable sequence with normal clips, markers, bins, and paths, the result can move through the rest of the post pipeline like any other Premiere project. ## Choose an installation method The project also offers a [Desktop bundle route](https://premiere-pro-mcp.com/docs/) for Claude Desktop. That route is convenient because the released bundle contains the local server, while you download the Premiere connector separately. If you're setting up a single Claude Desktop workstation and want the shortest path, the bundle can be a good first option. Use the manual setup when you need to document the setup, configure a different MCP client, or keep the package version pinned. Cursor, VS Code / Copilot, Claude Desktop, and other MCP clients can use this style of local server configuration if they support custom MCP servers. The manual setup has three moving parts: - Node.js 20.19 or newer on the workstation. - The `premiere-pro-mcp@1.29.0` package run through `npx`. - The package’s installer for the Premiere-side [CEP compatibility bridge](https://github.com/leancoderkavy/premiere-pro-mcp/). The CEP bridge is the part that makes Premiere reachable from the local MCP server. Installing it isn't the same as merely downloading a ZXP file, because a ZXP asset is just an extension package until an installer or the project’s documented command installs it. For the manual setup, use the package command, not a mix of steps from another repository. ## Install the CEP compatibility bridge Start with Premiere closed, or be prepared to restart it after the install, and confirm Node is current enough: ```bash node --version ``` You need Node.js 20.19 or newer. Then run the documented installer command for this package version: ```bash npx --yes premiere-pro-mcp@1.29.0 --install-cep ``` This installs the Premiere CEP compatibility bridge for the MCP server. The bridge is a local Premiere extension panel that allows the MCP server and Premiere to communicate. The project maintainer documents the bridge as the compatibility route for Premiere Pro 2020 through 2026 on Windows and macOS. On our Mac, the installer set Adobe’s `PlayerDebugMode` preferences to allow unsigned CEP extensions. This applies to the CEP host, not just this one panel, so install a connector you trust. It lets the local bridge run inside Premiere; it does not upload media. This package disables raw ExtendScript by default. After the bridge install, run the project’s diagnostic command: ```bash npx --yes premiere-pro-mcp@1.29.0 --doctor ``` Treat `--doctor` as a local package and configuration readiness report. It checks the local setup; you'll verify whether the assistant can connect to Premiere later with the connection tool. If it says the bridge or environment isn't ready, fix that before editing. Don't compensate with commands from a different Premiere MCP project, because the package names and global command behavior can overlap. ## Add the MCP server to your client In Claude Desktop 4.4212.0, open **Settings > Desktop app**, choose **Manage** beside Extensions, then find **Local MCP servers > Edit config**. Add this server entry to the configuration file: ```json { "mcpServers": { "premiere-pro-leancoderkavy": { "command": "npx", "args": [ "--yes", "premiere-pro-mcp@1.29.0" ] } } } ``` Merge it into the existing settings file for your client, and don't replace other servers unless that's intentional. The server name `premiere-pro-leancoderkavy` is useful because it makes the package identity clear inside clients that show multiple MCP servers. Restart the MCP client after changing the config. If your client has a reconnect or refresh action for MCP servers, use it, but a full restart is the simplest way to remove doubt during the first setup. ## Open the Premiere extension Launch Premiere Pro and open a new project or a disposable copy of an existing project, then open the installed extension from Premiere’s extension menu: Window > Extensions > MCP for Adobe Premiere Pro The panel should show **Connector running**, which is the Premiere-side confirmation. It tells you the bridge panel is alive inside Premiere, but it doesn't yet prove that your assistant can inspect the project through MCP. Next, use your MCP client to inspect the server capabilities before asking it to edit anything. Ask the assistant to call `get_capabilities` and summarize the available Premiere capability profile. This should tell you whether the assistant sees inspection tools, editing tools, export-related tools, filesystem-related tools, and any gated or disabled unsafe scripting capabilities. Then run the read-only connection test: ```text Safely check my Premiere connection with verify_premiere_connection. Make no changes. ``` The important part is “make no changes,” because you want a clean connection response before the assistant imports media, creates sequences, or saves a project. If the extension isn't Running, the MCP client can't verify the connection, or the capabilities look like the wrong package, stop there and re-check the Node version, the pinned MCP JSON, the installed CEP bridge, and whether Premiere was restarted after installation. On an empty project, our first connection check returned `needs_attention` because there was no active sequence. The MCP server and Premiere connector were both connected. Once we created and opened the test sequence, the same check returned `ready`. Read the individual component results before treating every `needs_attention` response as an installation failure. ## Build a three-clip timeline Use three short matching 24 fps test files that you can afford to throw away: camera test clips, generated slates, or sample media. Each source should be at least five seconds long, and this test uses exactly five seconds, or 120 sequence frames, from each clip. Put them somewhere with stable local paths, not a temporary downloads folder that may move later. For our test, we generated three six-second H.264 clips at 1920 × 1080 and 24 fps, each with stereo 48 kHz audio. We used the first five seconds of each. The sample project is named `Aspect_MCP_Three_Clip_Tutorial.prproj`. Create a new Premiere project or save a copy of a blank test project. Give the assistant an explicit request like this: ```text In the open Premiere project, import these three local 24 fps media files: /path/to/clip_01.mov /path/to/clip_02.mov /path/to/clip_03.mov Create a 24 fps non-drop-frame sequence named MCP_Three_Clip_Test with sequence start timecode 00:00:00:00. Use these sequence settings even if Premiere offers to match a clip. Use exactly the first five seconds, or 120 sequence frames, of each clip. Place them in this order on V1 and their linked audio on A1, with no gaps and no overlaps. The first clip should run from 00:00:00:00 to 00:00:05:00, the second from 00:00:05:00 to 00:00:10:00, and the third from 00:00:10:00 to 00:00:15:00. Add sequence markers at the opening and at each cut: 00:00:00:00, 00:00:05:00, and 00:00:10:00. Save the project only after reporting what you changed. ``` For this test, don't use arbitrary mixed-frame-rate or mismatched media. If the files are longer than five seconds, say “use the first five seconds” rather than “use the whole clip,” and if they aren't matching 24 fps test files, choose different test files before running this exact check. For a real workflow, specify the intended delivery format and sequence settings. The expected result is simple: one named 24 fps non-drop-frame sequence starting at 00:00:00:00, [three clips of five seconds](https://premiere-pro-mcp.com/demo/) or 120 sequence frames each, total duration of 15 seconds, markers at the opening and each cut, and imported project items pointing to the three source paths. ## Inspect the result in Premiere The assistant’s response is useful, but your team should inspect the edit in Premiere before you trust the setup. Open the sequence and check the sequence settings from Sequence > Sequence Settings. For this test, confirm the sequence is 24 fps, non-drop-frame, and starts at 00:00:00:00. Also confirm the frame size, pixel aspect ratio, fields, audio sample rate, and preview settings match the test settings you specified. For real projects, confirm Premiere used the intended delivery settings rather than silently creating a sequence from mixed media defaults. Then inspect the timeline positions. In the Timeline panel, zoom in enough to see the clip boundaries. The first clip should start at the beginning of the sequence. In the 24 fps test sequence, the first cut should land at 00:00:05:00, or sequence frame 120; the second cut should land at 00:00:10:00, or sequence frame 240; and the sequence should end at 00:00:15:00, or sequence frame 360. Use the time ruler, playhead timecode, and clip edges, because the point is to confirm there are no one-frame gaps, overlaps, or unintended trims. Also ask the assistant for a readback of the active sequence structure. You want a report that matches what Premiere shows: - Clip 1: 00:00:00:00 to 00:00:05:00. - Clip 2: 00:00:05:00 to 00:00:10:00. - Clip 3: 00:00:10:00 to 00:00:15:00. - Sequence markers: 00:00:00:00, 00:00:05:00, 00:00:10:00. In this 24 fps non-drop-frame test, those timecodes correspond to 0, 120, 240, and 360 sequence frames, so each clip is 120 frames long. For markers, open the Markers panel and select the sequence. You should see three sequence markers, not clip markers inside individual source clips. In the Timeline panel, the markers should appear on the sequence ruler at the opening and at both cut points. If your team uses marker names or colors for review, repeat the test with those conventions once the basic placement works. For media paths, select the imported items in the Project panel and inspect their properties. You can also use list view metadata columns if your workspace exposes file path metadata. Confirm the project items point to the intended local files, not duplicate transcodes, temporary downloads, or files on another editor’s machine. This matters because Premiere will show offline media later if those paths move or if you hand the project to another system without the same mounted root. Finally, save, close, and reopen the project. A clean reopen shouldn't trigger missing media relink prompts, so open the test sequence again and confirm the clips, markers, and paths survived the round trip. This confirms that the result is an editable Premiere project, not just a one-session automation result. In our reopened sample, the connector reported video and linked audio at 0–5, 5–10, and 10–15 seconds. The sequence was 1920 × 1080 at 24 fps, and the offline-media check returned zero missing files. The screenshot above shows the three clips and sequence markers after reopening. We verified the timeline structure and on-screen result; we did not export and assess a finished video. ## Use shared source media without breaking paths If your team [stores source media in Aspect](/blog/aspect-workflows/aspect-adobe-premiere-pro), keep the AI timeline operation and the media handoff as separate responsibilities. Aspect can hold the shared media library, make footage searchable, expose media context to an external assistant through Aspect MCP, and mount files so editors work from consistent paths. Premiere Pro MCP is the editor-side integration that turns local media paths and edit instructions into timeline operations. A clean handoff looks like this: use Aspect to [find the right clips](/features/asset-intelligence), transcript moments, or selects; make those files available through the mounted project path; then give Premiere Pro MCP the local mounted paths and requested timeline ranges. When every editor uses the same mounted root, the resulting Premiere project is much less likely to open offline on another workstation. For proxy workflows, keep the same discipline. Premiere supports ingest and proxy workflows so teams can work with optimized media while preserving originals for finishing. Whether the source comes from shared storage, mounted cloud media, or local editorial drives, tell the assistant to import the same paths your team expects Premiere to use. ## Common mistakes Most first-run problems are setup mismatches. Resolve these common mistakes before using a real project: - `get_capabilities` shows an unexpected tool set or server identity: re-check that the MCP JSON uses `premiere-pro-mcp@1.29.0`. - Window > Extensions > MCP for Adobe Premiere Pro is missing: the CEP bridge didn't install correctly, or Premiere needs a restart. - `verify_premiere_connection` fails: the MCP client can see the server, but the server can't reach the active Premiere bridge. - The assistant imports media from the wrong location: the prompt used ambiguous paths, or you or the assistant selected the files from a temporary location. - The reopened project shows offline media: the source paths moved, the mount root changed, or someone opened the project on a workstation without the same media access. Resolve these on the three-clip test. Don't debug them inside a live episode, client spot, or finishing project. ## What to try next Once you've checked that the three-clip sequence saves and reopens correctly, try a ten-clip stringout, a selects sequence with named markers, or organizing clips into bins. Choose one task you need for your project. Give the assistant the relevant file paths, clip order, time ranges, and marker instructions, then inspect the result in Premiere before asking it to do more. ## Visual references and setup guides - [Watch the maintainer's demo](https://premiere-pro-mcp.com/demo/). The original video page includes the demonstration's scope and limitations. - [Connector installation and troubleshooting](https://premiere-pro-mcp.com/docs/). Use the setup instructions for the selected package, including its CEP installation and doctor commands. - [Tool reference and source code](https://github.com/leancoderkavy/premiere-pro-mcp/). Check the selected connector's capabilities and requirements without mixing instructions from another Premiere MCP project.