Repo MCP

hetpatel-11/Adobe_Premiere_Pro_MCP

MCP server that lets Codex, Claude and other MCP clients operate local Adobe Premiere Pro projects through a CEP panel bridge, with 283 catalog tools.

  • 669 GitHub stars
  • TypeScript
  • ⚖️ MIT
  • 🎯 Intermediate
View on GitHub (opens in a new tab) Setup guide
npx skills add hetpatel-11/Adobe_Premiere_Pro_MCP --skill premiere-pro-mcp
hetpatel-11/Adobe_Premiere_Pro_MCP preview image

What it is

MCP Bridge for Adobe Premiere Pro is a local Node.js MCP server paired with a CEP panel inside Premiere. Clients call tools; the server generates ExtendScript, writes it to a bridge directory, and the panel runs it in Premiere and writes results back. It exposes 283 catalog tools via search_tools / get_tool_schema / invoke_tool, plus context resources and guided prompts. CEP is the supported production bridge; the bundled UXP plugin is experimental.

Who it's for

  • Video editors who want to drive Premiere Pro from Codex, Claude Code, Claude Desktop or other MCP clients
  • Developers building AI-assisted editing workflows on a local Premiere Pro install
  • Users who want agents to handle ingest, timeline edits, effects, captions, audio and export tasks

Requirements

Requirements

  • Node.js 20+
  • Adobe Premiere Pro 2020+ (actively used and tested on Premiere Pro 26.0)
  • Premiere Pro, the MCP client, and the npm package on the same computer
  • CEP bridge started via Window > Extensions > MCP Bridge (CEP)

Setup

  1. Install the package and CEP bridge

    Install the npm package globally, install the CEP bridge (also enables the Adobe CEP debug setting and configures supported local MCP clients), then run the doctor check.

    bash
    npm install -g adobe-premiere-pro-mcp
premiere-pro-mcp --install-cep
premiere-pro-mcp --doctor

  2. Start the bridge in Premiere

    Restart Premiere Pro, open Window > Extensions > MCP Bridge (CEP), set the bridge directory shown by the installer, and start the bridge. Then ask the client to run verify_premiere_connection without making changes.

  3. Configure another MCP client manually

    For clients the installer doesn't configure, point the client at the global command. To opt out of anonymous telemetry, add "env": { "PREMIERE_MCP_TELEMETRY": "0" } to the server entry.

    json
    {
  "mcpServers": {
    "premiere-pro": {
      "command": "premiere-pro-mcp"
    }
  }
}

  4. Optional: install the Agent Skill

    The included skill teaches agents to install, verify and use the MCP safely.

    bash
    npx skills add hetpatel-11/Adobe_Premiere_Pro_MCP --skill premiere-pro-mcp

Examples

Verify the connection first

Prompt
prompt
Run `verify_premiere_connection`. Make no changes.

Expected output: Read-only check that the CEP bridge responded; returns the Premiere build, open project and active sequence.

Add transitions

Prompt
prompt
Add cross dissolves to every cut on video track 1.

Expected output: Example editing prompt from the README covering transition tools.

Razor the timeline

Prompt
prompt
Razor the interview sequence at 12.5 seconds across all audio and video tracks.

Expected output: Uses timeline cutting tools such as razor_timeline_at_time / razor_all_tracks.

Export the active sequence

Prompt
prompt
Export the active sequence as FCP XML.

Expected output: Maps to the interchange export tools such as export_as_fcp_xml.

Install the Codex plugin from a clone

bash
bash
codex plugin marketplace add .
codex plugin add premiere-pro-mcp@adobe-premiere-pro-mcp

What it does: Bundles MCP configuration and the Premiere editing skill; still requires the local CEP bridge.

Pros & cons

Pros

  • Pro:Broad coverage: 283 catalog tools spanning project setup, ingest, timeline editing, effects, keyframes, captions, audio, and exports
  • Pro:Progressive discovery keeps the default tool list small (search_tools, get_tool_schema, invoke_tool), with PREMIERE_MCP_TOOLSET=full to list everything
  • Pro:Read-only verify_premiere_connection and a --doctor command support safe setup checks
  • Pro:Multiple install paths: npm, Codex plugin, Claude Code plugin, Claude Desktop .mcpb bundle, and source

Cons

  • Con:Must run on the same computer as Premiere Pro and the MCP client; the bridge uses local file polling
  • Con:The UXP plugin is experimental and not installed by the CLI; CEP is the only supported bridge
  • Con:Documented host limits: Premiere 26 has no scripting API to remove effects, and the DOM often can't read existing caption text

Images

hetpatel-11/Adobe_Premiere_Pro_MCP preview image
hetpatel-11/Adobe_Premiere_Pro_MCP preview image · hetpatel-11/Adobe_Premiere_Pro_MCP on GitHub · MIT
hetpatel-11/Adobe_Premiere_Pro_MCP preview image