How to Set Up Codex with Premiere Pro MCP

Use the same computer for Codex, the server, the CEP connector, and Premiere. This direct MCP configuration is an alternative to the repository plugin; choose one route so the server is not registered twice. It requires Node.js 20.19 or newer.

Codex does not control Adobe Premiere Pro by default. This repository includes an installable Codex plugin that bundles the local Premiere Pro MCP server configuration with a safety-oriented editing skill. The plugin still needs the separate CEP connector because that connector carries supported requests between the local server and the open Premiere session.

Use this setup from a clone of the repository, on the same computer as Codex and Premiere. The first goal is a live, read-only connection check, not a complex edit. Have a duplicate project or a small test sequence ready before you approve any supported mutation.

From a local clone of the Premiere Pro MCP repository, add the repository as a Codex plugin marketplace, then install the Premiere plugin: codex plugin marketplace add . followed by codex plugin add premiere-pro@premiere-pro-mcp. This registers the packaged MCP configuration for Codex; do not copy a configuration from an unrelated Premiere bridge.

Next, install the local CEP connector with the versioned package command from the current project README. The current release command is npx -y premiere-pro-mcp@1.14.9 --install-cep. The CEP installer is separate from the Codex plugin and is required for the local MCP server to communicate with the running Premiere host.

Restart Premiere Pro, open the project you intend to inspect, and open Window > Extensions > MCP for Adobe Premiere Pro. Then begin a new Codex session so it picks up the installed plugin configuration. Keep the initial connection local; the public operator-managed HTTP service is not a general relay to the project open on your workstation.

The default CEP route targets Premiere Pro 2020–2026 on Windows and macOS. UXP functionality is capability-gated on compatible hosts and does not replace the CEP setup needed for this first connection.

First ask Codex to inspect the available capabilities, then ask: Safely check my Premiere connection with verify_premiere_connection. Make no changes. When it succeeds, inspect the active project or sequence before proposing an edit. If it returns a diagnostic, resolve that specific condition instead of retrying a mutating request.

For a later supported change, name the sequence, target tracks, source clips, expected output, and no-change boundaries. Ask for a plan or preview where available, approve only the exact target you reviewed, and inspect returned state or diagnostics afterward. The plugin provides an integration path; it does not turn every operation into a host-proven result.