Premiere Pro Full MCP v0.2.0

English · 한국어

Premiere Pro Full MCP is a local, capability-gated MCP server for Adobe Premiere Pro 2026 on Windows. It combines the documented Premiere UXP API, a constrained CEP/ExtendScript bridge, experimental QE discovery, and a fail-closed native Windows UI agent.

This is an unofficial community project and is not affiliated with or endorsed by Adobe Inc. “Full” means the supported API surface is inventoried and routed; it does not mean every UI feature is scriptable in every host state.

English

Quick start for Windows

Requirements: Windows 10/11 x64, Premiere Pro 26.3 or later, Creative Cloud Desktop, and Codex Desktop or the Codex CLI. Node.js is not required for the packaged runtime.

1. Download premiere-pro-full-mcp-v0.2.0-windows.zip from the latest release. Verify its adjacent .sha256 file, then extract it.

2. Close Premiere Pro, open PowerShell in the extracted premiere-pro-full-mcp-0.2.0 folder, and run:

   powershell -NoProfile -ExecutionPolicy Bypass -File .\Install.ps1

   The installer verifies every packaged file, installs only in the current user profile, registers premiere_pro_full_mcp with Codex, and opens the bundled CCX.

3. Approve the independent-plugin warning in Creative Cloud Desktop. Restart Premiere, then open Window > UXP Plugins > Premiere Pro Full MCP.

4. On first use, click Pair with installed helper… and select %LOCALAPPDATA%\PremiereMCP\app\runtime-bootstrap.json. UXP remembers only the file permission; the session token is not stored in the CCX.

5. Restart Codex and call the host/capability inspection tools. Run Doctor if the bridge is not connected:

   powershell -NoProfile -ExecutionPolicy Bypass -File "$env:LOCALAPPDATA\PremiereMCP\app\tools\Doctor.ps1" -CheckLive

The executables and PowerShell scripts are not Authenticode-signed. Windows may show SmartScreen warnings. The release uses a separate RSA-signed update manifest, exact asset size/SHA-256 bindings, and an in-package SHA-256 manifest. The bundled CEP compatibility bridge carries an Adobe ZXP package signature, so installation does not enable CEP developer mode. The initial download still depends on GitHub HTTPS and the published checksum; do not bypass a warning if the checksum or source is unexpected.

Update and uninstall

# Download and install the newest authenticated GitHub release
powershell -NoProfile -ExecutionPolicy Bypass -File "$env:LOCALAPPDATA\PremiereMCP\app\tools\Update.ps1"

# Recoverable removal; pairing/workspace data is preserved
powershell -NoProfile -ExecutionPolicy Bypass -File "$env:LOCALAPPDATA\PremiereMCP\app\tools\Uninstall.ps1"

Updates reject signature, repository, tag, name, size, digest, prerelease, and downgrade mismatches. Remove the CCX separately in Creative Cloud Desktop > Plugins > Manage Plugins.

Safety and capability contract

• Documented UXP is preferred. CEP fills typed compatibility gaps, QE is experimental, and Windows UI Automation is the last resort.

• Failed mutations are never replayed through another backend automatically.

• Sequence export uses the documented UXP encoder path but does not trust a host Promise that can remain pending after rendering; success requires a changed, non-empty output file that remains stable across repeated observations. Existing outputs are rejected unless an explicitly approved overwrite policy is implemented.

• R2/R3 operations use short-lived, scope-bound, single-use approval IDs and an independent trusted Windows dialog.

• Raw ExtendScript, arbitrary QE/object paths, raw UI selectors/clicks, shell commands, and credential extraction are not public MCP operations.

• Listeners bind to localhost, CEP envelopes are HMAC authenticated through a DPAPI CurrentUser broker, and release artifacts never contain runtime bootstrap material.

• Filesystem work is confined to explicitly approved canonical roots and rejects reparse-point escapes.

• No telemetry is collected. Logs and ledgers exclude prompts, arguments, results, tokens, project paths, media names, and personal identifiers.

The generated Adobe 26.3 inventory contains 69 roots and 761 callable members. The final live full-surface baseline matched all 761 IDs. Of 312 deterministic read-only calls attempted, 281 succeeded and 31 failed closed because the required method, root, or session handle was unavailable. Another 151 risk-bearing entries were preview-only and 298 context-dependent entries were skipped with explicit reasons. See live validation.

Development

Requirements: Node.js 20.19+ (Node 24 preferred), .NET 8 SDK, Premiere Pro 26.3+, and Adobe UXP Developer Tool.

npm ci
npm run inventory:adobe
npm run check
npm run test:coverage
dotnet test .\windows-ui-agent\tests\PremiereMcp.WindowsUiAgent.Tests.csproj --configuration Release
npm run validate:uxp-plan

Release builds require a clean Git worktree and the dedicated private signing key under %LOCALAPPDATA%\PremiereMCP. The private key is never committed or uploaded to GitHub Actions. See deployment, security, and contributing.

한국어

Windows 빠른 설치

요구 사항은 Windows 10/11 x64, Premiere Pro 26.3 이상, Creative Cloud Desktop, Codex Desktop 또는 Codex CLI입니다. 배포 ZIP에는 자체 포함 네이티브 런처와 번들 MCP가 들어 있어 별도 Node.js 설치가 필요하지 않습니다.

1. 최신 릴리스에서 premiere-pro-full-mcp-v0.2.0-windows.zip과 .sha256을 내려받아 해시를 확인하고 압축을 풉니다.

2. Premiere Pro를 종료하고 압축을 푼 폴더에서 다음 명령을 실행합니다.

   powershell -NoProfile -ExecutionPolicy Bypass -File .\Install.ps1

3. Creative Cloud Desktop에서 독립 플러그인 설치 경고를 승인합니다. Premiere를 재시작한 뒤 창 > UXP 플러그인 > Premiere Pro Full MCP를 엽니다.

4. 첫 실행 때 **Pair with installed helper…**를 누르고 %LOCALAPPDATA%\PremiereMCP\app\runtime-bootstrap.json을 선택합니다. CCX에는 세션 토큰이 포함되지 않습니다.

5. Codex를 재시작합니다. 연결되지 않으면 다음 Doctor를 실행합니다.

   powershell -NoProfile -ExecutionPolicy Bypass -File "$env:LOCALAPPDATA\PremiereMCP\app\tools\Doctor.ps1" -CheckLive

설치기는 패키지 전 파일의 해시를 검증하고 현재 사용자 영역만 변경하며, 기존 설치와 Codex 설정을 실패 시 복원합니다. CCX 설치를 나중에 하려면 -SkipCcxLaunch, Codex 등록을 생략하려면 -SkipCodexRegistration을 사용합니다.

CEP 호환 브리지는 Adobe ZXP 방식으로 별도 서명되어 있으며, 설치기는 CEP 개발자 모드를 활성화하지 않습니다. EXE와 PowerShell 스크립트에는 Authenticode 서명이 없으므로 게시된 SHA-256과 RSA 릴리스 서명을 확인해야 합니다.

보안 및 지원 범위

이 프로젝트는 “Premiere의 모든 기능이 모든 상황에서 무조건 성공한다”고 주장하지 않습니다. 공개 API 표면 전체를 목록화하고, 라이브 검증된 경로만 지원으로 표시하며, 프로젝트 상태·미디어·플러그인·로그인·권한이 필요한 경로는 명확하게 실패하거나 보류합니다. UXP·CEP·QE·UI 자동화의 검증 범위는 각각 분리해 보고합니다.

취약점은 공개 이슈가 아니라 저장소 Security > Report a vulnerability에서 비공개로 신고해 주세요. 토큰, 실제 프로젝트, 사용자 경로, 미디어 이름은 이슈나 로그에 첨부하지 마세요.

Support

If Premiere Pro Full MCP saves you time, you can support continued development, host-version testing, and security maintenance on Ko-fi.

MIT License. Copyright (c) 2026 muhwagwa0112.