| FMRS | 54 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 11 / 20 | 14 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 |
|---|
| Setup experience | 12 / 20 | 15 / 20 |
|---|
| Best for | - Editors already using Premiere Pro who want to drive editing with natural language
- Users who need repeatable, scripted batch operations in Premiere
- Developers using MCP clients such as Codex, Claude Code, or Claude Desktop
- Teams chaining ingest, timeline work, and delivery checks into agent workflows
| - Individuals or teams who prioritise privacy and offline operation and do not want data leaving the machine
- Users who share memory across multiple MCP clients such as Claude Code, Claude Desktop, Hermes Agent, OpenClaw, Cursor, Codex and Gemini CLI
- Scenarios that need encrypted storage, a hash-chained audit log and verifiable vault migration
- Users who want low-latency recall, a bundled embedding model and no extra LLM calls inside the memory layer
|
|---|
| Not for | - Users without a local Premiere Pro install or who cannot run Node.js 20+
- Cloud or remote-machine setups, since Premiere, the client, and this package must be on the same computer
- Users expecting fully automatic professional-grade finished edits with no editorial judgment
- Users needing Adobe-official support or Marketplace-certified plugins, as CEP archives are unsigned or self-signed
| - Users who need cloud multi-device sync or a hosted team memory service; moving between machines means locking the vault and copying the file
- Users who expect the server itself to run an LLM that extracts facts and decides what to remember; Compartment explicitly keeps no LLM inside and leaves that to the host model
- Users who cannot keep a passphrase safe or who need a recovery path if it is lost, since Compartment never generates a password, seed or recovery phrase
- Deployments that require network transports such as SSE or streamable-http; this server is stdio only and opens no ports
|
|---|
| Required permissions | - Read and write the /tmp/premiere-mcp-bridge bridge directory
- Write the ~/.premiere-mcp-bridge/config.json configuration file
- Install a CEP extension on the user's machine and enable the Adobe CEP debug setting
- Modify local MCP client configuration such as Claude Desktop and GitHub Copilot in VS Code
- Read and write local Premiere projects, media files, and exported files
- Invoke local ffmpeg when detect_silence is used
- Send anonymous usage telemetry by default (install id, OS, package version, tool name, success or failure)
| - Read and write the vault file under the user's home directory, by default ~/.compartment/memory.vault, and its sibling settings file
- Access the session directory holding the unlock credential (configurable with COMPARTMENT_SESSION_DIR), which also carries the shared embedding process's Unix socket
- Optionally use the macOS keychain (compartment unlock --keychain is an explicit opt-in, and it survives reboots)
- Write or merge an mcpServers entry into each MCP client's own configuration file, taking a byte-exact backup first
- Install a PostToolUse hook for Claude Code that captures memory files the agent writes
- Serve a read-only dashboard on 127.0.0.1 behind a one-time random URL token
|
|---|
| Risks and side effects | - Tools really modify the Premiere project; deletions such as delete_project_item, delete_multiple_project_items, and remove_from_timeline are irreversible unless undone promptly.
- Advanced tools such as execute_extendscript and evaluate_expression can run arbitrary script and must only be used with trusted inputs and explicit intent.
- A self-signed or unsigned CEP archive only confirms archive integrity; it is not Adobe Marketplace approval or a public trust guarantee.
- The MCPB bundle is unsigned and should only be installed from this repository's GitHub Releases.
- Anonymous telemetry is on by default; project names, media paths, arguments, and results are not sent, and it can be disabled in the panel or with PREMIERE_MCP_TELEMETRY=0.
- Premiere scripting does not cover every UI operation; some results may be quantized or rejected by the host and should be read back for verification.
- The bundled UXP panel is an experimental preview and is not a replacement for the validated CEP bridge.
| - A leaked passphrase means the encrypted content can be decrypted; Compartment generates no recovery phrase and cannot recover a lost passphrase
- Enabling the memory_unlock tool places the passphrase in the model's context, which is why it is off by default
- If a 2FA keyfile is lost, for example a USB stick, the vault cannot be opened even with the passphrase
- `export --plaintext` writes the vault as unencrypted JSONL, so that file must be handled carefully
- Memory content can come from untrusted sources; recall wraps memories with a notice that they are stored data and content can be marked quarantined, but the host agent must still treat memory as data to limit prompt-injection risk
- The capture hook and client integration write into the user's own settings files, although the implementation backs up and merges rather than replacing
|
|---|
| Supported clients | Claude Desktop, Claude Code, Codex, GitHub Copilot in VS Code, Cursor | Claude Desktop, Claude Code, Hermes Agent, OpenClaw, Cursor, VS Code, Codex, Gemini CLI, Cline, Roo Code, Zed, OpenCode, LM Studio, AnythingLLM, BoltAI, Goose, Kiro |
|---|
| Tools | 100 | 14 |
|---|