Adobe Premiere Pro MCP

Use this skill when working with the Adobe Premiere Pro MCP server from hetpatel-11/AdobePremierePro_MCP.

Core Rules

• Use the MCP tools for Premiere operations; do not invent ExtendScript unless the MCP tool surface is missing the needed operation.
• Default MCP tools/list is a small always-on set. Call searchtools (BM25 query or regex pattern), then invoketool with the exact name. PREMIEREMCPTOOLSET=full lists every tool.
• Prefer read-only discovery first: getprojectinfo, listsequences, listprojectitems, getactive_sequence, and relevant resource reads.
• Use real imported media. If the user asks to edit with assets, verify file paths exist, import them with import_media, then place the imported project item IDs on a sequence.
• Keep the temp directory consistent across the MCP server and CEP panel: /tmp/premiere-mcp-bridge unless the user explicitly configured another path.
• Ask before destructive or externally visible actions: deleting clips/media, overwriting exports, closing projects, saving over important project files, or sending files elsewhere.
• For generated/demo edits, prefer creating a new clearly named sequence instead of modifying the user's active sequence.
• If a tool returns success: false, report the exact error and run diagnostics before retrying blindly.

Install Workflow

If the user asks you to install or set up the MCP:

1. Check the OS. The automated installer is macOS-focused.
2. Clone or open the repo:

git clone https://github.com/hetpatel-11/Adobe_Premiere_Pro_MCP.git
cd Adobe_Premiere_Pro_MCP

1. On macOS, run:

npm run setup:mac

1. For non-macOS or manual client setup, run:

npm install
npm run build

1. Register the MCP server in the user's client with:

command: node /absolute/path/to/Adobe_Premiere_Pro_MCP/dist/index.js
env: PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridge

For Codex, prefer:

codex mcp add premiere_pro --env PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridge -- node /absolute/path/to/Adobe_Premiere_Pro_MCP/dist/index.js

Premiere Bridge Startup

After installing:

1. Restart the MCP client if it reads config only at startup.
2. Restart Premiere Pro.
3. Open Window > Extensions > MCP Bridge (CEP).
4. Set Temp Directory to /tmp/premiere-mcp-bridge.
5. Click Save Configuration.
6. Click Start Bridge.
7. Confirm the bridge panel says Premiere is ready before running editing tools.

If Premiere is not running, you can install/build/register the MCP, but tell the user live tool verification requires Premiere and the CEP bridge panel.

Verification

Run local checks:

npm run setup:doctor

If Premiere is running and the bridge is started, verify with safe read-only calls:

• getprojectinfo
• list_sequences
• listprojectitems

For deeper validation in a disposable project, create a test sequence with createsequencefromclips or createsequence plus a real .sqpreset path, then call list_sequences and confirm it exists. Do not call blank sequence creation without a preset because newer Premiere versions can open a native dialog that blocks CEP.

Editing Strategy

• Start by understanding the project: project info, active sequence, existing media, tracks, markers, and selected sequence.
• Build a plan in concrete Premiere operations before changing anything.
• For rough cuts, import media first, then use createsequencefromclips so Premiere derives settings without a native dialog. Use createsequence only with a real .sqpreset; use duplicate_sequence with clearContents=true when an existing sequence defines the intended settings.
• For product or brand spots, prefer assembleproductspot or buildbrandspotfrommogrtandassets when the user's request fits those workflows.
• For black-and-white looks, use apply_effect with Black & White rather than generic saturation-only changes.
• For timeline cuts, prefer sequence-aware tools and include sequenceId when available.
• Export only after confirming output path, format/preset, and overwrite behavior.

Troubleshooting

If commands time out or report bridge errors:

1. Confirm Premiere is open.
2. Confirm Window > Extensions > MCP Bridge (CEP) is open and bridge is started.
3. Confirm both sides use the same temp directory.
4. Run:

npm run setup:doctor

1. Ask the user to click Run Diagnostics in the CEP panel.
2. Read /tmp/premiere-mcp-bridge/premiere-mcp-diagnostics-latest.json if it exists.
3. Remove stale command/response files only if they are clearly old and the bridge is stopped or idle.

Common fixes:

• ENOENT on temp directory: create /tmp/premiere-mcp-bridge, save config again, restart bridge.
• Tool succeeds in Premiere but reports failure: run list_sequences or the relevant list tool to confirm state before retrying.
• Empty or malformed temp directory config: set the field to the path only, not JSON or an env assignment.