Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Nothing to run from here
Premiere-MCP-IMT + SKILLS — Premiere Pro for AI agents is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
249
downloads a day
local
runs on your machine
2k
downloads in 30d
What it does
Let an AI assistant (Claude Desktop, Cursor, ChatGPT, Google Antigravity or any MCP client) work inside your running Adobe Premiere Pro: read the project and its sequences, cut, trim, move and ripple clips, apply effects, transitions and keyframes, add markers and captions, reframe, check frames and export — from plain language.
Every Adobe UI language · vision: masks and keyframes by sight · a large skills library · built for generative features. Premiere-MCP-IMT works with every UI language Adobe ships, and the agent sees the frame: it looks at exported frames, draws Object Masks on the people or parts it sees — a click for a whole person, a lasso for a face; add, subtract, track (macOS) — sets speed keyframes (Time Remapping) by dragging them into place on the timeline, and checks keyframed motion frame by frame. Premiere's scripting has no API for masks or speed keyframes; none of the other Premiere MCP servers we compared creates Object Masks, and Adobe's own AI Assistant in Premiere (beta) documents neither.
Two parts: the MCP server — about 440 readback-verified operations behind nine tools, no telemetry; and the skill — how to drive Premiere safely, where scripting ends, and how to use Premiere's own AI tools: Generative Extend, the Generative Media Tool, Object Mask, Speech to Text and Paper Edit, captions, Enhance Speech, Search, the AI Assistant, Auto Reframe — plus recipes that combine them.
Runs locally next to Premiere Pro on macOS and Windows: install it as described in the GitHub README (npm package @immersive-media-technologies/premiere-mcp-imt, or the Claude Desktop extension). By Immersive Media Technologies · Apache-2.0.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user pr-mcp-imt-premiere-pro-for-ai-agents '--' npx -y @immersive-media-technologies/premiere-mcp-imt
# 2 — ask your agent for something these tools do
# plan_cross_app_workflow
Premiere-MCP-IMT + SKILLS — Premiere Pro for AI agents costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Premiere-MCP-IMT + SKILLS — Premiere Pro for AI agents as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user pr-mcp-imt-premiere-pro-for-ai-agents '--' npx -y @immersive-media-technologies/premiere-mcp-imtReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
1 tool, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Plan an After Effects MOGRT or rendered-file handoff to Premiere using existing tools. Returns ordered dependencies, separate approvals, required evidence, and manual render stops. Local-only planning; never executes steps, issues approval tokens, or claims host readiness.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workflow | string | yes | Supported After Effects to Premiere handoff to plan. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Premiere-MCP-IMT + SKILLS — Premiere Pro for AI agents or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 1.3.1 · scanned 7 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings16 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestd9105ef698da1c40c562edea7a315bfa3973fc27541894d3358ea7c583b48d78
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
dist/locale/premiere-ui-names.d.ts (2 KB) was not read: over the file-count budget.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can start a fixed program (a process-spawning capability, not arbitrary code execution)
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestd9105ef698da1c40
Scanned2026-11-07
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.3.1. Pin a release below and the command asks for exactly that one.
1.3.1
6 Nov 2026
latestNo release note was published with this version.
1.3.0
6 Nov 2026
No release note was published with this version.
1.2.0
5 Nov 2026
No release note was published with this version.
1.1.1
28 Oct 2026
No release note was published with this version.
1.0.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Premiere-MCP-IMT + SKILLS — Premiere Pro for AI agents can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.