PremiereProMCP

Published: July 11, 2026

Control Adobe Premiere Pro from Claude, Cursor, or any MCP-compatible AI client — real timeline editing, not just project metadata.

Premiere Pro MCP (PPMCP) Control Adobe Premiere Pro from Claude, Cursor, or any MCP-compatible AI client — real timeline editing, not just project metadata. Developer: CaYaDev · cayadev.com [!IMPORTANT] To install: go to Releases, download PPMCP-Setup-x.x.x.zip, extract it, then double-click Setup.bat. That single file runs the whole installer. Everyone (recommended): Setup ZIP from Releases Open GitHub Releases. Download PPMCP-Setup-x.x.x.zip. Extract the folder → double-click Setup.bat. The wizard shows install folder, version, and optional CEP Text Bridge. If PPMCP is already installed, Setup offers: Update / reinstall to this version Uninstall completely When finished, open the personalized guide (real full paths on your PC): %APPDATA%\PPMCP\HOW-TO-USE.txt %APPDATA%\PPMCP\HOW-TO-CONNECT.txt %APPDATA%\PPMCP\mcp-config-snippet.json Setup is pure PowerShell (built into Windows) — no third-party installer, commercial-safe. The ZIP bundles portable Node.js — you do not need to install Node yourself. You do need Adobe UXP Developer Tool once (free) to load the Premiere panel: https://developer.adobe.com/premiere-pro/uxp/plugins/distribution/install/ https://developer.adobe.com/photoshop/uxp/2021/devtool/installation/ Search: Adobe UXP Developer Tool download Maintainers: build the ZIP Needs only Node.js + npm. Output: dist-release/PPMCP-Setup- .zip Developers: install from this repo Or (Node already installed): installer\Setup.bat or installer\install.bat Load plugin/manifest.json in UXP Developer Tool. Point MCP at server/dist/index.js. Details: INSTALL.md. Connect your MCP client PPMCP is a local stdio MCP server — a Node process on your own PC that your AI client talks to directly. It is not a hosted "remote MCP connector", so the "Add custom connector" → Remote MCP server URL flow you may see in Claude's Connectors settings does not apply here. Point your client at a local command instead. After running Setup, your exact ready-to-paste paths are already generated...