1 findingStatic scanned
Premiere Pro MCP
kavykun · MCP server
MCP server for Adobe Premiere Pro with 384 core AI video editing tools, a guarded After Effects MOGRT studio, and a capability-aware UXP bridge for supported Premiere workflows.
Not claimed by its maker. Is this yours? Prove it and answer the findings
From the maker
From the README of premiere-pro-mcp 1.18.1
The registry now serves 1.19.0. Everything measured on this page describes 1.18.1.
Findings, provenance and the install command are records of the scanned version, not the one npm would give you today. Treat them as history until this listing is rescanned. Registry checked 2026-10-03.
What else was checked
Publisher and name
Nothing found across 4 checks run. Checked 2026-09-28.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- eval (README.md:1504)
- dynamic Function constructor (README.md:1505)
- node child_process (scripts/build-claude-desktop.mjs:5)
- python subprocess (scripts/build-workflow-starter-kit.py:24)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
- Tool description integrity
- nothing to read
- Pattern set 1.0 matched nothing on 2026-10-03, but none of the descriptions the package ships runs to 120 characters, so there was little for a rule to read.
- It reads the descriptions the package ships, not what the server says when it runs, and a clean description is not the same thing as a safe tool.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Tool descriptions are read with pattern set v1.0, published with every rule, its sources and how often it has been wrong.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
What it does
MCP server for Adobe Premiere Pro with 384 core AI video editing tools, a guarded After Effects MOGRT studio, and a capability-aware UXP bridge for supported Premiere workflows.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 1.18.1, the file with digest sha512-Wn+w3i5fbk8navdpZwUeoy37F+jgaphW58qQDPK0rRv9WsknaVq1ESzi5DNjivXQMDy91EQLV85rqrDI+R159Q==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"premiere-pro-mcp": {
"command": "npx",
"args": [
"-y",
"premiere-pro-mcp@1.18.1"
]
}
}
}Or run it directly.
npx -y premiere-pro-mcp@1.18.1Pinned to 1.18.1, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
12,932 installs last month · build provenance signed · no published advisories · checked 2026-10-03
Where this came from
- Registry
- npm
- Package
- premiere-pro-mcp
- Version read
- 1.18.1
- Resolved
- 2026-09-25
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/premiere-pro-mcp)About this listing
- Kind
- MCP server
- Category
- Content
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-09-24
Similar MCP servers
All MCP serversVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.