Source review · Updated October 3, 2026

Choose a Premiere Pro MCP server for your workflow.

Start with your operating system, connection method, and the edit you need to complete. A larger tool catalog alone cannot tell you whether an operation works on your Premiere host.

This guide is maintained by leancoderkavy/premiere-pro-mcp. It compares five public projects and is not an independent benchmark. The Higgsfield package README was reviewed on October 3, 2026. The other external projects retain their linked README revisions reviewed on September 15, 2026. We have not run their tools in Premiere for this comparison.

Check the package name before installing

Our project is MCP for Adobe Premiere Pro, installed from premiere-pro-mcp and maintained at leancoderkavy/premiere-pro-mcp. The similarly named adobe-premiere-pro-mcp and @higgsfield_org/premiere-mcp packages are separate projects. Match the package, repository, and client configuration before following a guide.

For this project, the default CEP route serves local Premiere workflows, while the UXP preview adds authenticated, capability-gated documented APIs. Use the published release facts and searchable tool reference to check the exact action you need.

Higgsfield / @higgsfield_org/premiere-mcp

Setup and bridge: Published 0.1.3 README: Node.js 24+, local signed CEP extension, fnf-premiere configuration CLI, and fnf-premiere-mcp stdio executable.
Why evaluate it: Editors evaluating local project inspection, media import, bins, sequence and clip operations, track controls, and exports.
What to verify: The package describes testing on macOS / Premiere 26.5.1; Windows support is experimental. Reviewed October 3, 2026 from the npm README; no independent host test was performed.

Read this project’s source documentation

leancoderkavy / premiere-pro-mcp

Setup and bridge: Local Node.js server with CEP compatibility and capability-gated UXP tools.
Why evaluate it: Editors who want a searchable tool reference, guided setup, workflow recipes, and explicit released-versus-source availability.
What to verify: Review the recorded assembly workflow, then verify your own host connection. The recording covers one workflow on Premiere 26.5.0.

Read this project’s source documentation

hetpatel-11 / Adobe_Premiere_Pro_MCP

Setup and bridge: Node.js 20+, Premiere 2020+, local CEP panel; UXP is described as experimental.
Why evaluate it: Clients that benefit from a small always-on surface with search_tools / invoke_tool routing, guided prompts, and multilingual documentation.
What to verify: The README lists 283 tools and an installer/doctor workflow. Those are project claims, not independent host certification.

Read this project’s source documentation

ayushozha / AdobePremiereProMCP

Setup and bridge: Go orchestration, Rust media services, Python intelligence, and a TypeScript CEP bridge.
Why evaluate it: Developers evaluating script-to-timeline workflows, asset matching, EDL planning, captions, and broader media automation.
What to verify: The README distinguishes 1,064 schemas, 932 host commands, and a curated 72-tool standard profile. These are different units; the larger compatibility surface is not uniformly certified.

Read this project’s source documentation

antipaster / Adobe-Premiere-Pro-MCP

Setup and bridge: Windows, Node.js 18+, Premiere 2023+; Node server connects over WebSocket to a CEP panel.
Why evaluate it: Windows users exploring a batch installer, editing and caption tools, and optional ElevenLabs voiceover integration.
What to verify: The README advertises 170+ tools and says tested on Premiere 2026. Optional voice services need separate configuration; test your exact actions locally.

Read this project’s source documentation

Compare the same task on the same host

Record your Premiere version, OS, bridge, package version, and enabled tool profile.
Use a duplicate project and the same three sample clips for each evaluation.
Inspect the connection, assemble a sequence, add markers, and read back clip positions.
Check the native timeline and saved project. Record unsupported actions and failures alongside successes.

Separate registered schemas, default exposed tools, and live supported operations. Stars indicate community interest; they do not establish reliability or feature parity.

Evaluate this project before installing

Watch the recorded workflow and inspect its receipt, search the tool catalog, or read the release and compatibility facts. Ready to connect? Follow the installation guide.