Install, verify, troubleshoot, and operate the Adobe Premiere Pro MCP server. Use when a user wants an agent to set up Premiere MCP, connect Claude Code/Codex/Claude Desktop, control Premiere, import media, build sequences, edit timelines, apply effects, or diagnose bridge issues.

Adobe Premiere Pro MCP Use this skill when working with the Adobe Premiere Pro MCP server from hetpatel 11/Adobe Premiere Pro 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 search tools (BM25 query or regex pattern), then invoke tool with the exact name. PREMIERE MCP TOOLSET=full lists every tool. Prefer read only discovery first: get project info , list sequences , list project items , get active 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: 3. On macOS, run: 4. For non macOS or manual client setup, run: 5. Register the MCP server in the user's client with: For Codex, prefer: 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: If Premiere is running and the bridge is started, verify with safe read only calls: get project info list sequences list project items For deeper validation in a disposable project, create a test sequence with create sequence from clips or create sequence 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 create sequence from clips so Premiere derives settings without a native dialog. Use create sequence 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 assemble product spot or build brand spot from mogrt and assets 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: 5. Ask the user to click Run Diagnostics in the CEP panel. 6. Read /tmp/premiere mcp bridge/premiere mcp diagnostics latest.json if it exists. 7. 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.

premiere-pro-mcp