adobe-premiere-pro-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 2 tools tried
Contacts while installing and starting: adobe-premiere-mcp-telemetry.hetkp8044.workers.dev
What it contacted
adobe-premiere-mcp-telemetry.hetkp8044.workers.dev: usually analytics or error reporting
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y adobe-premiere-pro-mcp@1.2.11
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
2 tools that take no input and look read-only were called once with nothing. 1 returned a result.
search_tools | Returned a result under 0.1 s · 5,234 characters |
list_sequences | No usable answer tool reported an error: { "success": false, "error": "MCP Bridge is not running. Open Adobe Premiere Pro. The MCP Bridge panel auto-starts when Premiere ope |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
search_tools query, pattern, limit, detail
Search the Premiere tool catalog with a BM25 natural-language query or a regex pattern, then call invoke_tool. Use this instead of expecting 280 editing tools in the MCP tool list. Empty query lists categories. Default 5 matches.
get_tool_schema name
Return the full JSON input schema for one Premiere tool name from search_tools. After reading it, call invoke_tool.
invoke_tool name, arguments
Run a Premiere tool by exact name. Use after search_tools. Hosts that only advertise the small always-on set cannot call trim_clip etc. as top-level MCP tools.
verify_premiere_connection launchIfNeeded
Readiness check for Premiere Pro and the MCP Bridge. Call this before any editing tool. If Premiere is installed and not running, this launches it and waits for the CEP panel, which auto-starts the bridge. If it fails, tell the user the nextStep and do not retry other tools.
list_sequences
Lists all sequences in the current Premiere Pro project with their IDs, names, and basic properties.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Files it wrote
/tmp/ .premiere-mcp-bridge/ update-check.json /tmp/ .premiere-mcp-bridge/ install-id /tmp/ .premiere-mcp-bridge/ telemetry-day.json
Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.
Install facts
| License | MIT |
|---|---|
| Needs | node >=20.0.0 |
| Source | not stated |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-W8xHNIkXAA8FSUu7AKwiO3Qy5kYgyHOLEms3oVJBZgstfEz97v3t1toChncoOvzKqH00PmOgHwfHzsSxRQjULA== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/adobe-premiere-pro-mcp)
New version out? Ask for a fresh report.