MCP for Adobe Premiere Pro
NPM · PREMIERE-PRO-MCP
Local-first MCP for supported Adobe Premiere Pro workflows; start with a read-only connection check.
Available components
Last scanned (6 hours ago)
Scores higher than 30% of npm servers
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 13 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to leancoderkavy/premiere-pro-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.Unverified
Stability & Change Management0
- Stability not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, and comparing a partial copy would report the missing part as a change.Unverified
Tool Coverage0
- Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.Unverified
Tool Safety0
- Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.Unverified
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 4 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 1.00 ▲ functional
- 3 Nov 26 −11
- Known CVEs: pass → unverified ▼ security
- Dependency health: 1.00 → unverified ▼ functional
- Package version: 1.28.0 → 1.29.0 functional
- 1 Nov 26 0
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Package version: 1.25.0 → 1.28.0 functional
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 −27
- Stability: fail → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Package version: 1.24.3 → 1.25.0 functional
- Package version: 1.24.3 → 1.24.4 functional
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 +1
- Malware scan: unverified → pass ▲ security
- Package version: 1.24.2 → 1.24.3 functional
- 20 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 1.24.1 → 1.24.2 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/premiere-pro-mcp@1.29.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | leancoderkavy/premiere-pro-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/leancoderkavy/premiere-pro-mcp/.github/workflows/npm-publish.yml@refs/tags/v1.29.0 |
| Rekor log index | 3661879697 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2746a8e0db40d515acd50732502f6617daca539ba2c8d8bf85013cd83d082db73193782493f6e665e1c49e2b84175c1df440599ffa84d7c739dacf080 |
Background: How many MCP packages publish verified provenance →
Dependencies 13 packages
| Packages resolved | 13 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
The sandbox run completed and this package exposed no tools.
How do I install the MCP for Adobe Premiere Pro server?
MCP for Adobe Premiere Pro runs locally as an npm package, launched with npx -y premiere-pro-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · premiere-pro-mcp
claude mcp add leancoderkavy-premiere-pro -- npx -y premiere-pro-mcp
What is the MCP for Adobe Premiere Pro server?
MCP for Adobe Premiere Pro is listed in the public MCP registry as io.github.leancoderkavy/premiere-pro. Local-first MCP for supported Adobe Premiere Pro workflows; start with a read-only connection check. This page covers its npm package (premiere-pro-mcp).
Is the MCP for Adobe Premiere Pro server safe to use?
MCP for Adobe Premiere Pro scores 54 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the MCP for Adobe Premiere Pro server still maintained?
MCP for Adobe Premiere Pro is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MCP for Adobe Premiere Pro server under?
MCP for Adobe Premiere Pro declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.