premiere-pro-mcp

MCP音视频

提供方 IsaiahDupree

音视频 stdio · 本地进程 API Key 社区 / 第三方 Claude DesktopClaudeCursorWindsurf
查看接入方式

This MCP server enables AI assistants to directly control Adobe Premiere Pro via the Model Context Protocol, offering 269 tools for media import, timeline editing, effects and color correction, keyframing, and video export, making it ideal for film editing, short-form video production, and automated post-production workflows.

一句话选型结论

按资料字段整理

premiere-pro-mcp 属于音视频类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类音视频 传输方式stdio · 本地进程 鉴权API Key 部署方式本地部署
GitHub 星标 3 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

音视频
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

Blend Deployment Video Editing MCP Server TypeScript AI Automation Adobe Premiere Pro Timeline Editing Video Export Color Correction ExtendScript

支持客户端

适用场景

Blend DeploymentVideo EditingMCP Server

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
node /absolute/path/to/premiere-pro-mcp/dist/index.js

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 node,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
转写与字幕

把音视频转成文字和字幕。

音视频处理

裁剪、转码、拼接素材。

内容分发

把成品发到对应平台。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在音视频场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
premiere-pro-mcp当前 未标注 stdio · 本地进程 本地部署 有 2026-03-28
Ableton MCP B7b69a6a 16 stdio · 本地进程 本地部署 有 2026-05-17
Mini Max MCP 8 SSE · 服务端推送 远程部署 有 2026-05-18
LocalAI 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Youtube E0eb3510 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Voicemode MCP 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

音视频
字段来自项目仓库与公开索引,中文说明由本站标注
提供方IsaiahDupree上游标注的维护方 IsaiahDupree
分类音视频本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · node本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-03-28上游最后核验时间

详细介绍

19.4 KB
来自项目仓库与上游目录的原文,未做删改

Premiere Pro MCP Server

Give AI full control over Adobe Premiere Pro.

269 tools across 28 modules — the most comprehensive MCP server for video editing.


What is this?

An MCP (Model Context Protocol) server that lets AI assistants like Claude, Windsurf, Cursor, or any MCP-compatible client directly control Adobe Premiere Pro — importing media, editing timelines, applying effects, managing keyframes, exporting, and more.```
"Add the B-roll clips to V2, apply a cross dissolve between each, color correct them to match the A-roll, and export a 1080p ProRes."


The AI handles the entire workflow through 269 tools that cover nearly every ExtendScript and QE DOM API available in Premiere Pro.

---

## Quick Start

### 1. Install

**Option A — npm (recommended):**```bash
npm install -g premiere-pro-mcp

Option B — Clone from source:```bash
git clone https://github.com/ppmcp/premiere-pro-mcp.git
cd premiere-pro-mcp
npm install
npm run build


### 2. Install the CEP plugin

**If installed via npm:**```bash
premiere-pro-mcp --install-cep

If cloned from source:```bash
npm run install-cep


This symlinks the plugin into Premiere Pro's extensions folder and enables debug mode.

Manual installation (macOS)```bash
mkdir -p ~/Library/Application\ Support/Adobe/CEP/extensions
ln -s "$(pwd)/cep-plugin" ~/Library/Application\ Support/Adobe/CEP/extensions/MCPBridgeCEP

# Enable unsigned extensions (CSXS 9–14)
for v in 9 10 11 12 13 14; do
  defaults write com.adobe.CSXS.$v PlayerDebugMode 1
done

Manual installation (Windows)

  1. Copy the cep-plugin folder to %APPDATA%\Adobe\CEP\extensions\MCPBridgeCEP
  2. Open Registry Editor and set these DWORD values to 1:
    - HKEY_CURRENT_USER\Software\Adobe\CSXS.12\PlayerDebugMode
    - (repeat for CSXS.9 through CSXS.14)

3. Configure your MCP client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):```json
{
"mcpServers": {
"premiere-pro": {
"command": "node",
"args": ["/absolute/path/to/premiere-pro-mcp/dist/index.js"],
"env": {
"PREMIERE_TEMP_DIR": "/tmp/premiere-mcp-bridge"
}
}
}
}


Windsurf / Cascade

Add to your MCP server configuration:```json
{
  "premiere-pro": {
    "command": "node",
    "args": ["/absolute/path/to/premiere-pro-mcp/dist/index.js"],
    "env": {
      "PREMIERE_TEMP_DIR": "/tmp/premiere-mcp-bridge"
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project or global config:```json
{
"mcpServers": {
"premiere-pro": {
"command": "node",
"args": ["/absolute/path/to/premiere-pro-mcp/dist/index.js"],
"env": {
"PREMIERE_TEMP_DIR": "/tmp/premiere-mcp-bridge"
}
}
}
}


### 4. Start the bridge in Premiere Pro

1. Open (or restart) Premiere Pro
2. Go to **Window > Extensions > MCP Bridge**
3. Set the **Temp Directory** to match your MCP client config (e.g., `/tmp/premiere-mcp-bridge`)
4. Click **Start Bridge** — you should see a green "Running" status
5. Ask your AI assistant: *"What's my current Premiere Pro project?"*

---

## Architecture

**Local (stdio):**```
┌───────────────┐   stdio (MCP)   ┌──────────────┐   File-based IPC   ┌──────────────┐
│  AI Client    │ ◄──────────────► │  MCP Server  │ ◄────────────────► │  CEP Plugin  │
│  (Claude,     │                  │  (Node.js /  │   .jsx commands    │  (runs inside │
│   Windsurf,   │                  │   TypeScript) │   .json responses  │   Premiere)   │
│   Cursor)     │                  └──────────────┘                    └──────┬────────┘
└───────────────┘                                                             │ evalScript()
                                                                              ▼
                                                                       ┌──────────────┐
                                                                       │  Premiere Pro │
                                                                       │  ExtendScript │
                                                                       │  + QE DOM     │
                                                                       └──────────────┘

Remote (HTTP/SSE — Fly.io):```
┌───────────────┐ HTTP+SSE (MCP) ┌─────────────────────┐ File-based IPC ┌──────────────┐
│ AI Client │ ◄───────────────► │ MCP Server │ ◄────────────────► │ CEP Plugin │
│ (any MCP │ │ premiere-pro-mcp │ .jsx / .json │ (Premiere) │
│ client) │ │ .fly.dev │ shared volume └──────────────┘
└───────────────┘ └─────────────────────┘


1. AI client invokes an MCP tool (e.g., `add_to_timeline`)
2. MCP server generates ES3-compatible ExtendScript with helper functions prepended
3. Script is written to a `.jsx` command file in a shared temp directory
4. CEP plugin polls for command files, executes via `CSInterface.evalScript()`
5. Result JSON is written to a response file and returned to the AI

The file-based IPC bridge is simple, reliable, and works across macOS and Windows without network sockets.

---

## Tools (269)

### Discovery & Inspection (10 + 10)

| Tool | Description |
|------|-------------|
| `get_project_info` | Current project name, path, sequences, items |
| `get_active_sequence` | Detailed active sequence with all clips |
| `list_project_items` | All items in the project panel |
| `get_full_project_overview` | Comprehensive snapshot: bin tree, sequences, media types |
| `get_full_sequence_info` | Exhaustive sequence data: tracks, clips, effects, markers |
| `get_full_clip_info` | Everything about a clip: effects, keyframes, metadata |
| `get_timeline_summary` | Human-readable overview: duration, coverage %, effects |
| `search_project_items` | Filter by name, extension, offline status, color label |
| `get_premiere_state` | Full snapshot: project, sequence, playhead, selection |
| `inspect_dom_object` | Explore any Premiere Pro DOM object interactively |

### Project Management (26)

| Tool | Description |
|------|-------------|
| `save_project` / `save_project_as` / `open_project` | File operations |
| `create_project` / `close_project` | Project lifecycle |
| `import_media` / `import_folder` / `import_ae_comps` | Import media and AE comps |
| `create_bin` / `delete_bin` / `rename_bin` / `create_smart_bin` | Bin management |
| `import_sequences` / `import_fcp_xml` | Import from other projects |
| `create_bars_and_tone` | Generate bars & tone media |
| `set_scratch_disk_path` | Configure scratch disks |
| `consolidate_and_transfer` | Project Manager consolidation |

### Timeline & Editing (10 + 27 advanced)

| Tool | Description |
|------|-------------|
| `add_to_timeline` / `overwrite_clip` | Insert and overwrite edits |
| `ripple_delete` | Remove clip and close gap (QE) |
| `roll_edit` / `slide_edit` / `slip_edit` | Professional trim modes (QE) |
| `move_clip_to_track` | Move between tracks (QE) |
| `set_clip_speed_qe` / `reverse_clip` | Speed/reverse (QE) |
| `split_clip` / `trim_clip` / `move_clip` | Basic edits |
| `set_clip_properties` | Opacity, scale, rotation, position |
| `link_selection` / `unlink_selection` | Link/unlink A/V |

### Effects & Color (8)

| Tool | Description |
|------|-------------|
| `apply_effect` / `apply_audio_effect` | Apply by name (QE) |
| `remove_effect` / `remove_all_effects` | Remove effects |
| `color_correct` | Lumetri: exposure, contrast, temperature, etc. |
| `apply_lut` | Apply LUT files |
| `stabilize_clip` | Warp Stabilizer with configurable settings |

### Keyframes (8)

| Tool | Description |
|------|-------------|
| `add_keyframe` / `get_keyframes` | Create and read keyframes |
| `remove_keyframe` / `remove_keyframe_range` | Delete keyframes |
| `set_keyframe_interpolation` | Linear / Hold / Bezier |
| `get_value_at_time` | Query interpolated value at any time |
| `set_color_value` | Set color properties on effects |

### Export & Encoding (14)

| Tool | Description |
|------|-------------|
| `export_sequence` | Export via Adobe Media Encoder |
| `capture_frame` | Export frame as PNG, return as base64 image |
| `export_as_fcp_xml` / `export_aaf` / `export_omf` | Interchange formats |
| `encode_project_item` / `encode_file` | Direct encoding |
| `start_batch_encode` | Start render queue |

### Source Monitor & Playback (7 + 4)

| Tool | Description |
|------|-------------|
| `open_in_source` / `close_source_monitor` | Source monitor control |
| `insert_from_source` / `overwrite_from_source` | 3-point editing |
| `play_timeline` / `stop_playback` | Playback control (QE) |
| `play_source_monitor` | Play in source monitor |

### Selection & Clipboard (7 + 6)

| Tool | Description |
|------|-------------|
| `select_clips_by_name` / `select_clips_in_range` | Smart selection |
| `copy_effects_between_clips` | Copy effects via QE |
| `batch_apply_effect` | Apply effect to multiple clips |
| `set_blend_mode` | 27 blend modes |

### Media Properties (16)

| Tool | Description |
|------|-------------|
| `set_offline` / `has_proxy` / `detach_proxy` | Offline/proxy management |
| `set_override_frame_rate` | Override FPS |
| `set_scale_to_frame_size` | Auto-scale to sequence frame |
| `get_xmp_metadata` / `set_xmp_metadata` | Raw XMP access |
| `get_color_space` | Color space info |

### Sequence Management (11)

| Tool | Description |
|------|-------------|
| `create_sequence` / `create_sequence_from_preset` | Create sequences |
| `duplicate_sequence` / `delete_sequence` | Manage sequences |
| `auto_reframe_sequence` | Auto-reframe for social media |
| `attach_custom_property` | FCP XML custom properties |
| `unnest_sequence` | Replace nested sequence with its clips |

### Workspace & Captions (2 + 1)

| Tool | Description |
|------|-------------|
| `get_workspaces` / `set_workspace` | Switch workspace layouts |
| `create_caption_track` | Create caption/subtitle tracks |

### Scripting (6)

| Tool | Description |
|------|-------------|
| `execute_extendscript` | Run arbitrary ExtendScript (ES3) |
| `evaluate_expression` | Quick one-line eval |
| `send_raw_script` | Bypass security validation (advanced) |

### ...and 100+ more

Track targeting, batch operations, markers, audio levels, motion/transform, metadata, sequence settings, navigation, project analysis, and more. Run `get_project_info` to get started — the AI will discover what it needs.

---

## MCP Resources

The server exposes two LLM context resources:

| Resource URI | Description |
|-------------|-------------|
| `config://premiere-instructions` | Best practices: workflow order, timeline rules, effect tips, error handling |
| `config://extendscript-reference` | Complete ExtendScript API reference for writing custom scripts |

These are automatically available to MCP clients that support resources, giving the AI deep context about how to drive Premiere Pro effectively.

---

## Remote Deployment (Fly.io)

The server includes an HTTP/SSE transport (`src/http-server.ts`) for remote access via mcp-remote or any MCP client that supports Streamable HTTP.

A live instance is running at **https://premiere-pro-mcp.fly.dev**.

### Connect via mcp-remote```json
{
  "mcpServers": {
    "premiere-pro": {
      "command": "npx",
      "args": ["mcp-remote", "https://premiere-pro-mcp.fly.dev/mcp"]
    }
  }
}

Self-host on Fly.io```bash

Clone and deploy your own instance

git clone https://github.com/ppmcp/premiere-pro-mcp.git
cd premiere-pro-mcp
fly apps create your-app-name
fly deploy --remote-only

Optional: add bearer token auth

fly secrets set MCP_AUTH_TOKEN=your-secret-token


Then connect with:```json
{
  "mcpServers": {
    "premiere-pro": {
      "command": "npx",
      "args": ["mcp-remote", "https://your-app-name.fly.dev/mcp",
               "--header", "Authorization: Bearer your-secret-token"]
    }
  }
}

> Note: The file bridge still requires the CEP plugin to share the same PREMIERE_TEMP_DIR. For cloud deployments this means running a sync agent or using fly proxy / WireGuard to reach your local machine.


Environment Variables

Variable Description Default
PREMIERE_TEMP_DIR Shared temp directory for MCP ↔ CEP communication OS temp dir + /premiere-mcp-bridge
PREMIERE_TIMEOUT_MS Command timeout in milliseconds 30000
PORT HTTP port (HTTP/SSE transport only) 3000
MCP_AUTH_TOKEN Bearer token for HTTP transport auth (optional) unset

Project Structure```

premiere-pro-mcp/
├── src/
│ ├── index.ts # Entry point — stdio transport setup
│ ├── http-server.ts # Entry point — HTTP/SSE transport (Fly.io / remote)
│ ├── server.ts # MCP server — registers all 269 tools + 2 resources
│ ├── bridge/
│ │ ├── file-bridge.ts # File-based IPC (write .jsx, poll .json)
│ │ └── script-builder.ts # ExtendScript generator with ES3 helpers
│ ├── tools/ # 28 tool modules
│ │ ├── discovery.ts # Project discovery and queries
│ │ ├── project.ts # Project management and import
│ │ ├── media.ts # Media and proxy management
│ │ ├── sequence.ts # Sequence creation and settings
│ │ ├── timeline.ts # Timeline clip operations
│ │ ├── effects.ts # Effect application and color correction
│ │ ├── transitions.ts # Transition management (QE DOM)
│ │ ├── audio.ts # Audio levels and keyframes
│ │ ├── text.ts # Text overlays and MOGRTs
│ │ ├── markers.ts # Sequence and clip markers
│ │ ├── tracks.ts # Track add/delete/lock/visibility
│ │ ├── playhead.ts # Playhead, work area, in/out points
│ │ ├── metadata.ts # Metadata, XMP, color labels
│ │ ├── export.ts # Export, frame capture, encoding
│ │ ├── advanced.ts # QE DOM: ripple, roll, slide, slip, speed
│ │ ├── keyframes.ts # Keyframe CRUD and interpolation
│ │ ├── scripting.ts # Execute arbitrary ExtendScript
│ │ ├── inspection.ts # Deep project/sequence/clip inspection
│ │ ├── selection.ts # Clip selection utilities
│ │ ├── clipboard.ts # Copy effects, batch operations
│ │ ├── source-monitor.ts # Source monitor control
│ │ ├── track-targeting.ts # Track targeting, motion, audio props
│ │ ├── utility.ts # Batch ops, analysis, navigation
│ │ ├── health.ts # Connectivity ping
│ │ ├── workspace.ts # Workspace layout switching
│ │ ├── captions.ts # Caption track creation
│ │ ├── playback.ts # Timeline/source playback control
│ │ └── project-manager.ts # Project consolidation/transfer
│ └── resources/
│ └── extendscript-reference.ts # API reference for LLM context
├── cep-plugin/ # CEP panel that runs inside Premiere Pro
│ ├── CSXS/manifest.xml # Extension manifest (PPRO 14.0+)
│ ├── index.html # Panel UI
│ ├── main.js # Bridge polling and script execution
│ ├── host.jsx # ExtendScript entry point
│ └── CSInterface.js # Adobe CEP interface library
├── scripts/
│ └── install-cep.sh # CEP plugin installer (symlink + debug mode)
├── Dockerfile # Multi-stage Docker build for Fly.io
├── fly.toml # Fly.io deployment config
├── RESEARCH.md # API research and implementation status
├── CONTRIBUTING.md # Contribution guidelines
├── CHANGELOG.md # Version history
└── LICENSE # MIT License
```


Technical Details

Why CEP instead of UXP?

CEP (Common Extensibility Platform) provides full ExtendScript access in Premiere Pro, including the undocumented QE DOM — which is the only way to apply effects by name, perform ripple deletes, and do advanced trim operations. UXP in Premiere Pro is still maturing and lacks equivalent API coverage. CEP works across Premiere Pro 2020–2025+.

ExtendScript Compatibility

All generated scripts use ES3 syntax (var, manual for loops, no arrow functions, no let/const) since ExtendScript is based on ECMAScript 3. The buildToolScript() function prepends a library of helper functions to every script.

Security

  • Scripts are validated before execution — blocks eval(), new Function(), System.callSystem()
  • 500KB script size limit
  • send_raw_script bypasses validation for advanced users (with explicit opt-in)
  • Temp directory created with restricted permissions (mode 700)

QE DOM

Many tools use the undocumented QE DOM (enabled via app.enableQE()). These tools are marked with "Uses QE DOM" in their descriptions. The QE DOM provides capabilities unavailable through the standard ExtendScript API:

  • Apply effects and transitions by name
  • Ripple delete, roll/slide/slip edits
  • Set clip speed and reverse
  • Frame blending and time interpolation
  • Remove all effects from a clip

Troubleshooting

CEP plugin doesn't appear in Premiere Pro

  1. Verify debug mode: defaults read com.adobe.CSXS.12 PlayerDebugMode should return 1
  2. Check the plugin exists: ls ~/Library/Application\ Support/Adobe/CEP/extensions/MCPBridgeCEP
  3. Completely restart Premiere Pro (not just close/reopen the project)
  4. Check the CSXS version matches your Premiere Pro version

Commands timeout or hang

  1. Verify the CEP panel shows "Running" with a green dot
  2. Ensure temp directories match between MCP client config and CEP panel
  3. Check if Premiere Pro is busy (rendering, modal dialog open)
  4. Increase timeout: set PREMIERE_TIMEOUT_MS to 60000 or higher
  5. Try ping tool to test basic connectivity

AI client can't see tools

  1. Restart the AI client after editing config
  2. Verify the path to dist/index.js is absolute and correct
  3. Run node dist/index.js in a terminal to check for startup errors
  4. Ensure npm run build completed without errors

QE DOM tools fail

  1. QE tools require an active sequence — open one first
  2. Some QE operations are index-based and can fail if clips have been reordered
  3. Re-query the sequence structure after QE operations

Contributing

Contributions are welcome! See CONTRIBUTING.md for guidelines.


License

MIT — free for personal and commercial use.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
premiere-pro-mcp 怎么安装?

在客户端按下面的安装命令接入:node /absolute/path/to/premiere-pro-mcp/dist/index.js。装完在客户端配置里引用同一个包或端点。

premiere-pro-mcp 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

premiere-pro-mcp 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

premiere-pro-mcp 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

premiere-pro-mcp 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、Windsurf;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

premiere-pro-mcp 能提供哪些能力?

资料显示能力标签包括 Blend Deployment、Video Editing、MCP Server、TypeScript、AI Automation、Adobe Premiere Pro。具体工具清单以官方文档为准。

premiere-pro-mcp 需要什么运行环境?

运行时为 node;属于本地进程,需要在本机装好运行环境。

premiere-pro-mcp 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-03-28。