Skills/npm/premiere-pro-mcp

premiere-pro-mcp@1.30.0

VERIFIED· not started

Publisher claims: "MCP server for Adobe Premiere Pro with 447 core AI video editing tools, a guarded After Effects MOGRT studio, and a capability-aware UXP bridge for supported Premiere workflows." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher leancoderkavy · publishing for 260 daysInstalls 25,151Last detonated 6d ago
$claude mcp add premiere-pro-mcp -- npx -y premiere-pro-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
ALLOW_UNAUTHENTICATEDMCP_AUTH_TOKENMCP_OAUTH_ALLOWED_SUBJECTSMCP_OAUTH_AUDIENCEMCP_OAUTH_ISSUERMCP_OAUTH_JWKS_URIMCP_OAUTH_REQUIRED_SCOPESNODE_AUTH_TOKENNPM_TOKENPOSTHOG_API_KEYPREMIERE_UXP_TOKENTIMECODE_TOKENConfiguration, not credentials: AUDIO_KEYFRAME_READBACK, FLY_MACHINE_ID, FLY_REGION, KAV312_UNDO_INDEX, MCP_HTTP_HOST, MCP_PUBLIC_URL, MCP_TRUST_PROXY, npm_execpath, NPM_OTP, PASTE_ATTRIBUTES_MAX_KEYS_PER_PROPERTY, POSTHOG_DISTINCT_ID, POSTHOG_ENVIRONMENT, POSTHOG_HOST, PREMIERE_DEFAULT_SEQUENCE_PRESET, PREMIERE_MCP_DEBUG, PREMIERE_MCP_PROTOCOL_MODE, PREMIERE_MCP_TRANSPORT, PREMIERE_TEMP_DIR, PREMIERE_TIMEOUT_MS, PREMIERE_UXP_PORT
Where it talks to
premiere-pro-mcp.com (its own)Also posthog.com, adobe.com, purl.org, iptc.org — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names posthog.com, adobe.com, purl.org, iptc.org as well as its own vendor. The guard injects ALLOW_UNAUTHENTICATED, MCP_AUTH_TOKEN, MCP_OAUTH_ALLOWED_SUBJECTS, MCP_OAUTH_AUDIENCE, MCP_OAUTH_ISSUER, MCP_OAUTH_JWKS_URI, MCP_OAUTH_REQUIRED_SCOPES, NODE_AUTH_TOKEN, NPM_TOKEN, POSTHOG_API_KEY, PREMIERE_UXP_TOKEN, TIMECODE_TOKEN only into requests to premiere-pro-mcp.com (and its subdomains) and refuses the rest.

$vet-skills run --secrets ALLOW_UNAUTHENTICATED=premiere-pro-mcp.com,MCP_AUTH_TOKEN=premiere-pro-mcp.com,MCP_OAUTH_ALLOWED_SUBJECTS=premiere-pro-mcp.com,MCP_OAUTH_AUDIENCE=premiere-pro-mcp.com,MCP_OAUTH_ISSUER=premiere-pro-mcp.com,MCP_OAUTH_JWKS_URI=premiere-pro-mcp.com,MCP_OAUTH_REQUIRED_SCOPES=premiere-pro-mcp.com,NODE_AUTH_TOKEN=premiere-pro-mcp.com,NPM_TOKEN=premiere-pro-mcp.com,POSTHOG_API_KEY=premiere-pro-mcp.com,PREMIERE_UXP_TOKEN=premiere-pro-mcp.com,TIMECODE_TOKEN=premiere-pro-mcp.com -- npx -y premiere-pro-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-08 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 12 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
12sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-q1BZAP/task/home/.npm/_logs/2026-11-08T21_32_21_562Z-debug-0.log
12sclaimednot started: dependency install failed (exit 1); the server itself was not observed
12sprocessscript backend runs setup only
12sprocessno install scripts to re-run

Static findings

HIGH
Collapsed <details> block carrying instructionsREADME.md:1726 · Collapsed <details> block carrying instructions<summary><strong>CEP plugin doesn't appear in Premiere Pro</strong></summary> 1. Verify debug mode: - macOS: `defaults read com.adobe.CSXS.12 PlayerDebugMode` sFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
MEDIUM
npx invocation of non-well-known packagedist/doctor-repairs.js:18 · npx invocation of non-well-known package — may execute untrusted code+ "Install the signed MCPBridgeCEP.zxp from the GitHub release, or run `npx -y premiere-pro-mcp --install-cep`.");Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈83 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for premiere-pro-mcp@1.30.0 as of 6d ago. This is the package itself, not its dependencies.