ayushozha/AdobePremiereProMCP

git clone https://github.com/ayushozha/AdobePremiereProMCP.git
cd AdobePremiereProMCP && cp .env.example .env
just install && just proto && just build
just install-panel

Usage

• •Add {"mcpServers":{"premiere-pro":{"command":"./go-orchestrator/bin/premierpro-mcp","args":["--transport","stdio"]}}} to the MCP client config
• •Set MCP_TOOL_PROFILE (core, dialogue, captions, social, standard, all, unsafe) to tune the exposed tool surface
• •Run ./go-orchestrator/bin/premierpro-mcp --transport stdio to start the server

Key features

• ✓Script parsing, asset matching, EDL generation and pacing analysis for automated rough cuts
• ✓72 curated readback-first tools from a 1,064-tool schema registry covering timeline, media, audio, effects, captions, MOGRT and export
• ✓Four-language architecture: Go orchestrator, Rust media engine, Python edit intelligence, TypeScript CEP bridge
• ✓Readback verification and explicit unsupported errors for audited mutation routes
• ✓Duplicate-sequence recovery boundary with timeline snapshots and sequence versioning

Best for

AI-driven Adobe Premiere Pro editing automation: rough cuts, batch color grading, audio mixing, template-based edits and multi-format export.

Caveats

• ⚠A real Premiere Pro session is required to certify host mutations on a specific OS/build
• ⚠The TypeScript bridge must run on the host, not in Docker, because the CEP panel only accepts loopback WebSocket connections
• ⚠Arbitrary script/shell/file tools are hidden unless the unsafe profile is selected
• ⚠Full Windows service supervision is not yet implemented by the batch launcher