Cursor Premiere Pro setup

How to Set Up Cursor with Premiere Pro MCP

Connect Cursor to local Premiere Pro with a versioned MCP configuration, install the CEP connector, and verify the bridge before editing a project.

5 min read

Use Cursor on the computer running Premiere

Cursor can call this project's local MCP server, which passes supported operations to the separate Premiere connector. Install Cursor, Node.js, the MCP server, and the connector on the computer running your licensed Premiere application. Begin with a disposable project and an active sequence.

This guide uses a local stdio process. A Cursor cloud agent or a remote development environment does not automatically have access to the Premiere project on your desktop. The public product website is not a relay to your workstation.

Install and diagnose the Premiere connector

Use Node.js 20.19+ and run these commands in a local terminal. Fully quit Premiere before installing its connector. The versioned npm command selects premiere-pro-mcp from leancoderkavy; adobe-premiere-pro-mcp is a separate package whose global executable has the same name.

Restart Premiere, open Window > Extensions > MCP for Adobe Premiere Pro, and open your test project. The doctor command reports setup diagnostics; it does not prove that Cursor has reached the current Premiere session.

Install the CEP connector and inspect diagnostics
npx --yes premiere-pro-mcp@1.15.0 --install-cep
npx --yes premiere-pro-mcp@1.15.0 --doctor

Add one MCP entry to Cursor

Cursor supports project settings in .cursor/mcp.json and user-wide settings in ~/.cursor/mcp.json. Choose one scope. Merge this entry with existing mcpServers rather than replacing the whole file, then enable the server from Cursor's Customize page.

The first run may download the pinned npm release. If you already configured a different Premiere MCP entry, disable it while evaluating this one so the assistant does not receive two overlapping tool sets. Keep each project's connector and configuration together.

Cursor mcp.json entry for this published package
{
  "mcpServers": {
    "premiere-pro-leancoderkavy": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "--yes",
        "premiere-pro-mcp@1.15.0"
      ]
    }
  }
}

Verify the connection before a timeline edit

In a local Cursor Agent conversation, request the connection tool explicitly. Inspect the returned project, active sequence, connector, and readiness diagnostics. A tool listed by Cursor has been advertised by the server; it is not evidence that the corresponding host action has succeeded.

After the read-only check succeeds, choose a small inspection or preview workflow from the starter kit. Review arguments and results before approving a mutation. The tool reference explains source action names and availability, while your running session determines which calls are available.

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

Resolve setup failures from the returned evidence

Check the failing layer before retrying. Keep screenshots and reports free of private project paths, tokens, and client footage.

  • Server cannot start: confirm Node.js and npx are available to the local Cursor process. Restart Cursor after installing Node, and inspect the MCP startup output.
  • Invalid configuration: check JSON syntax, preserve existing entries, and confirm you edited the intended user or project settings file.
  • Tools appear but Premiere is disconnected: restart the CEP panel, open a project, and rerun the read-only connection check.
  • A UXP tool is absent: it requires an authenticated compatible UXP panel with the required host capability. The default CEP setup does not advertise every UXP addition.

Questions editors ask

Does Cursor need a remote MCP URL to edit local Premiere?

No. This guide uses local stdio so Cursor starts the server beside Premiere. The separate CEP connector is still required.

Where does the Cursor MCP configuration go?

Use .cursor/mcp.json in the project or ~/.cursor/mcp.json for user-wide settings. Choose one scope and preserve existing server entries.

Will the configuration change my Premiere project?

Adding the server does not itself request an edit. Later tool calls can change a project, so start with verify_premiere_connection and review each proposed operation.

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