Adobe_Premiere_Pro_MCP

Adobe Premiere Pro MCP. Tools for AI-driven video editing via MCP, for Codex, Claude, and other MCP clients.

Runs with mockssource: GitHubhomepageTypeScriptMITcommit ee31c3def7c3

TypeScript, MIT licensed. The project labels itself: adobe, adobe mcp, adobe premiere pro, adobe premiere pro mcp, ai automation, ai video editing, cep and claude code.

Adobe_Premiere_Pro_MCP runs, with stand-ins for the services it depends on. An Argusic agent installed it in 8 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The project builds with tsc, all 653 tests pass, the MCP server starts and responds to tools/list over stdio, and the CLI reports version and help correctly.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.10 (measured)
recorded runs
2
last tested
stars
924
forks
165
open issues
27
watchers
10
size
24 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing Adobe_Premiere_Pro_MCP, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • --version flag crashed with JSON import assertion error on Node 182 minutes
  • build_motion_graphics_demo test timed out at 30s in the full suite1 minute
Install time
8 minutes
Cold machine to finish
23 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npm test -- --runInBand exited 0, 653 passed, 32 suites passed; node dist/index.js responded to tools/list JSON-RPC; node dist/cli.js --version printed 1.2.8
Model tokens used
72,003
Exact commit tested
ee31c3def7c3
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

72,003
All 653 tests pass. Let me compile the final results.
Here's a summary of everything I did and observed:
**Install & Build** - `npm install` succeeded (Node 18 < 20 caused engine warnings, but all deps in…
**Errors found and fixed:**
1. **Test timeout** - `builds a motion graphics demo sequence` test had a 30s timeout that was too …
2. **CLI `--version` crash** - used `import(..., { with: { type: 'json' } })` which requires Node 2…
**Verification:**
- `npm test -- --runInBand` exited 0, **653 passed**, 32 suites passed
- Server starts and responds to MCP `tools/list` JSON-RPC
- `node dist/cli.js --help` prints usage
- `node dist/cli.js --version` prints `1.2.8`

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 8 minutes.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

Of the 5 adobe projects Argusic has installed and timed, Adobe_Premiere_Pro_MCP was the 3rd fastest to reach a running state, and 3 of 5 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.10
Argusic Runner1/3Runs with mocks92.000.05

Topics (from GitHub)

adobeadobe-mcpadobe-premiere-proadobe-premiere-pro-mcpai-automationai-video-editingcepclaude-codeclaude-desktopcodexcursorextendscriptmcpmcp-servermcp-toolsmodel-context-protocolpremiere-automationuxpvideo-automationvideo-editing

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/Adobe_Premiere_Pro_MCP.svg)](https://argusic.com/subject/adobe-premiere-pro-mcp)

Questions

Does Adobe_Premiere_Pro_MCP run?
Adobe_Premiere_Pro_MCP runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 8 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test Adobe_Premiere_Pro_MCP?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ee31c3def7c3. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Adobe_Premiere_Pro_MCP?
The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Adobe_Premiere_Pro_MCP take to install?
8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does Adobe_Premiere_Pro_MCP need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Adobe_Premiere_Pro_MCP?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does Adobe_Premiere_Pro_MCP compare with the alternatives?
Of the 5 adobe projects Argusic has installed and timed, Adobe_Premiere_Pro_MCP was the 3rd fastest to reach a running state, and 3 of 5 reached one at all.
Where is the evidence for Adobe_Premiere_Pro_MCP?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion