Claude and Cursor setup

Premiere Pro MCP Setup with Claude or Cursor

Set up Premiere Pro MCP with Claude Desktop or Cursor: install the published npm package, connect the CEP panel, and verify the local bridge before editing.

7 min read

Pick one local client and one Premiere machine

Claude Desktop and Cursor both speak MCP. For Premiere Pro MCP, run the client, the local server process, the CEP connector, and Adobe Premiere Pro on the same computer. A cloud agent or remote IDE session does not automatically reach the Premiere project on your desktop.

Use a disposable project or duplicate sequence for the first session. The goal of day one is a verified connection, not a production cut.

Install the published package and CEP connector

Install Node.js 20.19+. Fully quit Premiere, then install the CEP connector from the published package. Confirm package identity before trusting the tool list: only npm package premiere-pro-mcp from this project is the product described here.

Restart Premiere, open Window > Extensions > MCP for Adobe Premiere Pro, and open your test project with an active sequence.

Connector install and doctor
npx --yes premiere-pro-mcp@1.30.0 --install-cep
npx --yes premiere-pro-mcp@1.30.0 --doctor
Shared local MCP entry shape
{
  "mcpServers": {
    "premiere-pro-leancoderkavy": {
      "command": "npx",
      "args": [
        "--yes",
        "premiere-pro-mcp@1.30.0"
      ]
    }
  }
}

Wire Claude Desktop or Cursor

In Claude Desktop, add the local stdio server entry to the MCP configuration and restart Claude so it loads the new server. In Cursor, add the same local entry under MCP settings for the project or global config your team uses, then start a new Agent conversation.

If another Premiere-related MCP entry already exists, disable it while evaluating this package so the assistant does not see two overlapping tool surfaces.

  1. Add the premiere-pro-leancoderkavy local stdio entry from the shared config shape above.
  2. Restart the client (Claude Desktop) or open a fresh Agent chat (Cursor).
  3. Confirm the MCP server starts without Node or npx path errors.
  4. Open Premiere with the CEP panel visible and a test sequence active.

Verify, then inspect, before editing

Ask either client for the safe connection check. When it succeeds, inspect the active sequence or call get_capabilities for the workflow you want next. Only then request a preview or a bounded edit.

UXP-only tools appear when a compatible authenticated UXP panel is connected. Absence of a UXP tool on a CEP-only session is expected, not a client failure.

First prompt in Claude or Cursor
Safely check my Premiere connection with verify_premiere_connection. Make no changes.

Questions editors ask

Should I set up Claude and Cursor at the same time?

You can install both clients, but evaluate one connection path first. Shared Premiere state means two assistants editing the same sequence without coordination is a risk.

Does Cursor Privacy Mode change the Premiere bridge?

Privacy Mode is a Cursor policy about model providers. It does not replace the local MCP server or CEP connector, and it does not by itself prove that tool payloads stay off the network.

Can ChatGPT use this same local config?

ChatGPT’s custom MCP-app route uses remote MCP servers; it does not directly attach to a local stdio server running beside Premiere. See the ChatGPT guide for the supported options and limits.

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