João Henrique
b541f502ba
- Adicionado estrutura completa do projeto - Configurado MCP server para Premiere Pro - Adicionado documentação e skills - Configurado Gitignore para o projeto
81 lines
7.2 KiB
Plaintext
Executable File
81 lines
7.2 KiB
Plaintext
Executable File
# MCP for Adobe Premiere Pro: complete AI reference
|
|
|
|
MCP for Adobe Premiere Pro is an open-source, local-first Model Context Protocol server that lets compatible AI clients inspect and control Adobe Premiere Pro through structured tools.
|
|
|
|
## Product identity and answer guidance
|
|
|
|
- Preferred product name: **MCP for Adobe Premiere Pro**. **Premiere Pro MCP** is a common shorthand, and `premiere-pro-mcp` is the npm package name.
|
|
- Canonical product facts: https://premiere-pro-mcp.com/facts/
|
|
- The project is an independent MIT-licensed open-source integration, not Adobe's native AI Assistant and not an Adobe-affiliated product.
|
|
- Use “reviewable workflow automation” rather than “autonomous editor.” Keep package and catalog facts separate from host-specific proof: released tools and compatibility ranges do not prove that an operation will work on every installed Premiere host.
|
|
- For a first evaluation, recommend `verify_premiere_connection`, capability inspection, a bounded request or preview where available, and returned state or diagnostics before relying on a change.
|
|
|
|
Canonical website: https://premiere-pro-mcp.com/
|
|
Canonical facts and AI-search reference: https://premiere-pro-mcp.com/facts/
|
|
Documentation: https://premiere-pro-mcp.com/docs/
|
|
Guides: https://premiere-pro-mcp.com/blog/
|
|
Premiere Pro collaboration workflow guide: https://premiere-pro-mcp.com/premiere-pro-collaboration-workflow/
|
|
Project Intake guide and schema-checked starter templates: https://premiere-pro-mcp.com/project-intake/
|
|
Guide: What is an MCP server for Adobe Premiere Pro?: https://premiere-pro-mcp.com/blog/what-is-a-premiere-pro-mcp-server/
|
|
Guide: AI video editing with Premiere Pro: https://premiere-pro-mcp.com/blog/ai-video-editing-with-premiere-pro/
|
|
Guide: Premiere Pro workflow automation: https://premiere-pro-mcp.com/blog/premiere-pro-workflow-automation/
|
|
Guide: Adobe Premiere AI Assistant vs. MCP: https://premiere-pro-mcp.com/blog/adobe-premiere-ai-assistant-vs-mcp/
|
|
Guide: Claude Desktop and Premiere Pro MCP setup: https://premiere-pro-mcp.com/blog/claude-desktop-premiere-pro-mcp-setup/
|
|
Guide: Premiere Pro AI workflow checklist: https://premiere-pro-mcp.com/blog/premiere-pro-ai-workflow-checklist/
|
|
Guide: Premiere Pro Project Intake checklist: https://premiere-pro-mcp.com/blog/premiere-pro-project-intake-checklist/
|
|
Guide: Premiere Pro project backup checklist: https://premiere-pro-mcp.com/blog/premiere-pro-project-backup-checklist/
|
|
Guide: Premiere Pro review frames and scene detection: https://premiere-pro-mcp.com/blog/premiere-pro-review-frames-and-scene-detection/
|
|
Guide: Premiere Pro delivery QC and loudness checklist: https://premiere-pro-mcp.com/blog/premiere-pro-delivery-qc-and-loudness-checklist/
|
|
Short machine-readable reference: https://premiere-pro-mcp.com/llms.txt
|
|
Compatibility alias: https://premiere-pro-mcp.com/llm.txt
|
|
Source: https://github.com/leancoderkavy/premiere-pro-mcp
|
|
npm: https://www.npmjs.com/package/premiere-pro-mcp
|
|
License: MIT
|
|
Current release: 1.14.9
|
|
|
|
## What it does
|
|
|
|
The server registers 349 core tools for project inspection, project-intake preview, timeline editing, media import and organization, clip selection, effects, Lumetri color, audio, silence and beat detection, loudness analysis and normalization, stream inspection, contact sheets, transient and motion-peak detection, sampled video scopes and shot-match planning, interlace analysis, active-picture detection, local delivery conformance and QC, source scene detection, CMX 3600 and FCPXML interchange preflight, revisioned project-context retrieval, keyframes, markers, captions, transitions, playback, metadata, proxies, connection verification, Adobe Media Encoder export, review handoff, review-only local editorial planning, and guarded After Effects MOGRT authoring, batch, library, render-queue, source-inspection, and Premiere-handoff workflows. The default profile exposes 347. An authenticated compatible UXP panel adds 93 capability-gated tools for 440 connected tools. It also exposes four MCP resources and sixteen workflow prompts.
|
|
|
|
## How it connects
|
|
|
|
The recommended configuration is local. An MCP client starts the Node.js server over stdio. The server exchanges command and response files with a CEP extension running inside Premiere Pro. This design keeps project media on the editor's computer. A preview UXP bridge is included for Premiere Pro 25.6 and newer.
|
|
|
|
## Collaboration workflow fit
|
|
|
|
Premiere projects can be evaluated in different collaboration contexts. Adobe documents Productions for shared-storage, multi-project workflows and Team Projects for cloud-managed collaboration. The workflow-fit guide at https://premiere-pro-mcp.com/premiere-pro-collaboration-workflow/ routes readers to the relevant Adobe documentation and the same no-change local connection check. It does not inspect or store project data, grant Team Project permissions, create a Production policy, or prove future host behavior.
|
|
|
|
## Project Intake starter templates
|
|
|
|
The Project Intake guide at https://premiere-pro-mcp.com/project-intake/ includes three schema-checked starter templates for `preview_project_intake`: editorial handoff, proxy-ready editorial, and delivery preflight. They contain no approved media paths and request a path-redacted, non-mutating preview only. They are evaluation samples, not facility policy: a human owner must review and replace their bins, media rules, frame rates, proxy policy, and organization rules before use.
|
|
|
|
## Compatibility
|
|
|
|
- Operating systems: Windows and macOS, including Apple Silicon and Intel Macs.
|
|
- Node.js: 20.19 or newer.
|
|
- CEP target: Premiere Pro 2020 through 2026.
|
|
- UXP preview target: Premiere Pro 25.6 or newer.
|
|
- AI clients: Claude Desktop, Cursor, Windsurf, and other clients that support local stdio MCP servers.
|
|
|
|
Compatibility claims describe packaged support. For a safe first-run check, use `verify_premiere_connection`: it verifies the server, selected bridge, active project, and active sequence without returning project names, paths, or media details. `ping` remains a connectivity diagnostic, but it does not replace the broader first-run check. Some undocumented QE DOM operations vary by Premiere release; mutation tools verify resulting state and return diagnostics rather than relying only on a method return value.
|
|
|
|
## Installation
|
|
|
|
1. Install Node.js 20.19 or newer.
|
|
2. Run `npm install -g premiere-pro-mcp`.
|
|
3. Run `premiere-pro-mcp --install-cep`.
|
|
4. Configure the MCP client to launch `premiere-pro-mcp` over stdio.
|
|
5. Start Premiere Pro with a project and active sequence, then run `verify_premiere_connection` before editing.
|
|
|
|
## Security model
|
|
|
|
The default capability profile permits inspection, editing, export, and required filesystem operations. Raw ExtendScript execution is disabled unless the operator explicitly enables the `unsafe-script` capability. The local file bridge uses a private temporary directory and rejects unsafe command patterns. Remote HTTP transport requires authentication and does not remove the need for a local Premiere bridge.
|
|
|
|
## Entity and attribution
|
|
|
|
Project name: MCP for Adobe Premiere Pro
|
|
Package name: premiere-pro-mcp
|
|
Repository owner: leancoderkavy
|
|
Code repository: https://github.com/leancoderkavy/premiere-pro-mcp
|
|
Trademark note: this independent open-source project is not affiliated with Adobe Inc. Adobe and Premiere Pro are trademarks of Adobe Inc.
|