How to Set Up Premiere Pro MCP Safely

Premiere Pro MCP connects a compatible AI client to a running Adobe Premiere Pro session through a local server and a separate Premiere connector. The recommended arrangement keeps the AI client, MCP server, connector, Premiere, and project media on the same computer. It is not a hosted editing service and it does not make a cloud deployment control the Premiere project open on your workstation.

For the supported local path, use Windows or macOS, Premiere Pro 2020–2026, and Node.js 20.19+ when your chosen client does not use the released Claude Desktop bundle. Keep a duplicate project or small test sequence available for the first supported change. Compatibility and a successful installation do not prove every host operation on every machine.

For a compatible client without its own bundle, install the published package with npm, then run the connector installer: npm install -g premiere-pro-mcp, followed by premiere-pro-mcp --install-cep. The installer puts the per-user CEP connector in Premiere's extensions location and enables the required local debug setting. If you use Claude Desktop, the release bundle supplies the server, but the signed Premiere connector is still a separate install.

Restart Premiere after the connector is installed. With a project open, use Window > Extensions > MCP for Adobe Premiere Pro to open the connector. Do not move on to an edit request until the connector is available in the live host.

Your AI client needs a local MCP-server entry that launches premiere-pro-mcp. The common shape is a server named premiere-pro with command premiere-pro-mcp, but client configuration screens and file locations differ. Use the client's own MCP setup instructions rather than copying a configuration intended for another app.

Choose one client for the first check. Claude Desktop has a release bundle; Codex has a repository plugin; other clients may use the npm-based local configuration. Keep the client on the same machine as Premiere for this local setup. A public operator-managed HTTP endpoint is not a desktop relay for your local Premiere project.

Fully restart the AI client and Premiere, open a project, and select an active sequence. Then send this exact first request: Safely check my Premiere connection with verify_premiere_connection. Make no changes. It is deliberately read-only, so it separates an installation or bridge problem from an editing problem without requesting a project mutation.

If the check returns a diagnostic, resolve the reported connection, host, project, sequence, or capability condition first. If it succeeds, inspect the active project or sequence, then ask for a small bounded plan or preview before applying a supported operation. A tool being listed or called is not proof that a Premiere change completed.

When the read-only check fails, reopen both applications, confirm the correct Premiere project and active sequence are open, and confirm the connector appears under Premiere's Extensions menu. Share the returned diagnostic with support instead of screenshots of sensitive footage, project names, media paths, prompts, or credentials.

The local-first Premiere path does not change how your chosen AI client handles conversations or data. Review that client's privacy controls independently. Do not expose the MCP HTTP transport to the public internet without the authentication and edge controls documented for an operator-managed deployment.