Claude Premiere Pro setup

How to Set Up Claude with Premiere Pro MCP

Set up Claude with Adobe Premiere Pro using the local MCP bundle and CEP connector, then verify the bridge before requesting any supported edit.

9 min read

Before you install

Connect Claude Desktop to a running Premiere session with two separate downloads: the Claude bundle provides the MCP server, and the CEP connector provides the link to Premiere. Install both on the same Windows or macOS computer. This project is independent of Adobe and Anthropic.

Published package: v1.20.0. The CEP route targets Premiere Pro 2020–2026; individual operations remain host-dependent. UXP support is a separate capability-gated path and does not replace the first-install CEP route.

  • Use the desktop Claude app for the local bundle route. A connection configured in the browser is a different setup.
  • Choose a disposable project or a copy, open an active sequence, and keep the original edit recoverable.
  • The links below open the latest GitHub release. Download its .mcpb bundle and MCPBridgeCEP.zxp connector from the same release. The npm package published by this repository is premiere-pro-mcp; similarly named packages belong to other projects.

Install the Claude bundle and Premiere connector

The bundle includes its own local server runtime. The recommended bundle route does not require a separate Node.js installation. A managed Claude workspace may restrict custom extensions; follow the workspace administrator's policy.

  1. In Claude Desktop, open Settings > Extensions > Advanced settings. Choose Install Extension and select the downloaded .mcpb file. Complete the displayed configuration.
  2. Install MCPBridgeCEP.zxp using a ZXP installer you trust. If you do not have an installer, use the npm alternative in the next section.
  3. Fully quit and reopen Claude Desktop and Premiere Pro. Open your disposable project and select a sequence.
  4. In Premiere, open Window > Extensions > MCP for Adobe Premiere Pro. Older connector builds may use the label MCP Bridge. Keep the panel open.
  5. Start a new Claude conversation and run the connection-check prompt below before requesting an edit.

Alternative: install the connector with npm

Use this alternative if you need the connector installer or prefer to configure a local server manually. It requires Node.js 20.19 or newer. Run these commands in a terminal on the computer running Premiere. The connector installer enables the Adobe CEP debug setting required by this installation route.

If you already installed the Claude bundle, do not add a second Claude MCP entry for the same server. Use the commands to install and diagnose the connector, then continue with the bundle.

Install the published server and CEP connector
npx --yes premiere-pro-mcp@1.20.0 --install-cep
npx --yes premiere-pro-mcp@1.20.0 --doctor

Run the read-only connection check

Send this prompt in Claude. A tool appearing in the client proves discovery, not that the Premiere panel is connected. Read the tool result and stop if it reports a missing connector, project, sequence, or permission.

First prompt: check the local Premiere connection
Safely check my Premiere connection with verify_premiere_connection. Make no changes.
  • Installed: the server and connector are present.
  • Configured: the client knows how to start the local server.
  • Connected: the connector answers for the intended Premiere session.
  • Verified for this task: inspect the particular project, sequence, and capability before relying on a later operation.

Walk through your first project inspection

After the connection check succeeds, use this small inspection exercise. It asks for observable project state and leaves editing decisions for a later request. The downloadable starter kit contains synthetic clips for a disposable project; it is an evaluation sample, not a recorded host demonstration.

  1. Compare the reported sequence name and frame rate with the sequence open in Premiere.
  2. Compare the returned duration and track counts with the timeline. An unavailable field is not a successful check.
  3. If an identity or value disagrees, stop and resolve the connection or target before asking for a change.
  4. For a later edit, name the target, ask for a preview where supported, approve that exact change, and inspect the result.
Second prompt: inspect the active sequence
Inspect my open Premiere project and active sequence. Report the sequence name, frame rate, duration, video and audio track counts, and any unavailable fields. Make no changes. Do not export files or upload media.

Fix the failure you actually see

Use the failing layer to choose the next step. Avoid repeating an edit request while the connection remains unresolved.

  • Bundle installed, but tools missing: restart Claude Desktop, check Extensions for the enabled bundle, and start a new conversation. Check managed-workspace restrictions if custom extensions are unavailable.
  • No Premiere panel in the Extensions menu: confirm the separate CEP connector was installed for the current user, then fully restart Premiere. Installing the Claude bundle alone does not install this connector.
  • Connection timeout: keep the panel open, confirm Premiere is responsive, and check that the server and panel use the same bridge directory. Do not substitute a public hosted endpoint for a local bridge.
  • No active project or sequence: open a project and select the intended sequence, then repeat only the read-only check.
  • Unsupported tool or host capability: inspect the available capabilities and use a supported route. A larger catalog is not proof that a host supports an operation.
  • Need help: include OS, Premiere version, package version, and a redacted diagnostic. Remove project names, media paths, prompts, footage, tokens, and personal data before posting.

Understand what stays local

The recommended server, connector, and Premiere media path run on your computer. Claude's own conversation and tool-data policies still apply; local execution does not mean that every interaction with the assistant stays on-device. Review the client's privacy controls before sharing project context.

Keep the local installation distinct from the operator-managed hosted MCP service. The public website does not pair a cloud server with a visitor's Premiere session.

Questions editors ask

Do I need Node.js to connect Claude Desktop?

The released Claude Desktop bundle includes the local server, so the recommended Claude path does not require a separate Node.js install just to connect. Other clients may use the npm or manual setup route.

Does a successful connection check prove every Premiere tool works?

No. It confirms the connection path. Inspect current capabilities, keep the task small, and verify the returned state or diagnostics for the specific operation you need.

Can I use a client other than Claude Desktop?

Yes, if it supports local MCP servers. Cursor, VS Code or Copilot, Windsurf, and other compatible clients use their own guided or advanced setup paths.

Keep learning

Try the workflow starter kit

Use synthetic clips and a disposable project. Download the evaluation kit, follow this recipe, and compare the result yourself.

Get the sample media and promptNeed setup help?

A practical next step

Start with a safe Premiere connection check.

Connect your assistant, verify the local bridge without changing a project, then inspect the active sequence before requesting a supported edit.

Run a safe connection check