| FMRS | 54 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 9 / 20 | 10 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 11 / 20 | 18 / 20 |
|---|
| Documentation | 14 / 20 | 17 / 20 |
|---|
| Setup experience | 12 / 20 | 14 / 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
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| 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 needing to write to upstream databases (read-only)
- Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
- Users expecting all advanced features without API keys
|
|---|
| 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)
| - Requires internet access to query public biomedical APIs
- Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
- Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
|
|---|
| 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.
| - Upstream API rate limits may affect performance
- Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
- Features requiring API keys (e.g., OncoKB) may be incomplete without them
- Local binary installations need regular updates for compatibility
|
|---|
| Supported clients | Claude Desktop, Claude Code, Codex, GitHub Copilot in VS Code, Cursor | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 100 | 11 |
|---|