npm install guide

How to Install premiere-pro-mcp from npm (Package Name Check)

Install premiere-pro-mcp@1.15.2 from npm, verify its package identity, connect the local CEP panel, and run a read-only Premiere connection check.

6 min read

Who this guide is for

Use this guide when your MCP client needs a local npm server for Adobe Premiere Pro — Cursor, VS Code / Copilot, Windsurf, or another desktop client that accepts a command entry. If you can use the Claude Desktop bundle, prefer that path on the homepage install section; this page is the exact package route for npm.

Current public package: premiere-pro-mcp@1.15.2 (MIT, free).

Exact package name

Install this project with the unscoped name. Run these checks from a directory outside an existing source checkout: npm can otherwise prefer a local installation over the downloaded executable.

Install the package with version pin
npm i -g premiere-pro-mcp@1.15.2

Verify the package behind the command

This project's package is premiere-pro-mcp, not adobe-premiere-pro-mcp.

Both packages can expose a command named premiere-pro-mcp. A copied install tip or an older global binary can therefore start the wrong project. Before you configure a client:

  1. Confirm the package name is premiere-pro-mcp.
  2. Use npx --yes premiere-pro-mcp@1.15.2 in client configuration to select the intended package and version.
  3. Expect version 1.15.2, homepage premiere-pro-mcp.com, and source leancoderkavy/premiere-pro-mcp.
Verify the pinned package identity
npm view premiere-pro-mcp@1.15.2 name version homepage repository.url bin --json
npx --yes premiere-pro-mcp@1.15.2 --version
  • Both projects are separate open-source efforts; choose the package that matches the documentation you are following.
  • For a side-by-side package comparison, see premiere-pro-mcp vs adobe-premiere-pro-mcp.

Prerequisites

Claude Desktop remains the recommended easiest start when you want a self-contained bundle.

  • Node.js 20.19+ for the npm/npx route
  • Adobe Premiere Pro 2020–2026 on macOS or Windows
  • CEP connector as the default public first-run path (signed CEP package or --install-cep)
  • UXP is capability-gated for compatible Premiere 25.6.0+ workflows; it is not the default installer and does not replace CEP for first setup

Install the Premiere connector (CEP-first)

Your assistant talks to Premiere through a separate local connector. Fully quit Premiere before running the versioned installer below.

Alternatively, download the signed CEP package from the v1.15.2 release and open it with a trusted ZXP installer.

Then reopen Premiere and restart your assistant. Open a disposable project with an active sequence. In Premiere, confirm Window → Extensions → MCP for Adobe Premiere Pro.

Install CEP connector with versioned command
npx --yes premiere-pro-mcp@1.15.2 --install-cep

Configure the MCP client (versioned command)

For clients that use an mcpServers JSON object, merge this entry into the existing configuration. Preserve other server entries. Other clients, including Codex, use their own configuration format; follow the linked client guide.

Keep Premiere, the connector, and the client on the same computer. Restart the client after saving settings.

Client MCP configuration example
{
  "mcpServers": {
    "premiere-pro-leancoderkavy": {
      "command": "npx",
      "args": ["--yes", "premiere-pro-mcp@1.15.2"]
    }
  }
}

Safe first prompt (no edits)

Open a project and ask:

A verified connection still depends on a live local host bridge. Preview supported edits before you apply them.

First request
Safely check my Premiere connection with verify_premiere_connection. Make no changes.

If it does not connect

Work through Setup & recovery: restart both apps, confirm an active sequence, confirm the CEP panel is available, then re-run the safe prompt. Share connection state with support — not project media.

If the version command reports something other than 1.15.2, repeat it outside any existing repository or Node project. Also check the MCP client's working directory for an older local installation before trusting its tool list.

Questions editors ask

Is premiere-pro-mcp the same as adobe-premiere-pro-mcp?

No. Different packages and repositories. Both may register a premiere-pro-mcp command — verify the package name.

Should I install from Creative Cloud Marketplace?

No Marketplace listing is required for this project's CEP default path. Follow the release connector or --install-cep.

Does install upload my footage?

The recommended setup is local-first. The bridge exchanges commands and structured results; your assistant's separate privacy settings still apply.

Is speech-to-text / STT included in 1.15.2?

No. STT is not in public npm 1.15.2. Do not assume unreleased features are available in the published package.

Does this guide install unreleased tools from main?

No. These commands select the published 1.15.2 package. Check the product facts page for the separate released and development catalogs.

Keep learning

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