mcpcost

io.github.mrfentmen/adobe-premiere-mcp

adobe-premiere-mcp

Is the io.github.mrfentmen/adobe-premiere-mcp MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-27.

Control Adobe Premiere Pro video editing via ExtendScript.

alive probed 2026-11-15 · unchanged since 2026-10-27

11tools
1.5ktokens in Claude Opus 5.5
0.7 %of Claude's 200k window
0.6×the median server
301 msto initialize
8 msto list tools
Run it
npx -y @mrfentmen/adobe-premiere-mcp@1.0.2 (stdio, probed in a container with the network off)
Host
npmjs.com
Reports itself as
adobe-premiere-mcp 1.0.0
Capabilities
tools
Instructions
none
Of a 1M window
0.1 % of a 1M context window
Count
1.5k tokens in Claude Opus 5.5, exact, measured 2026-10-27. With the Claude Code prefix mcp__…__ on each tool name: 1.6k. The o200k_base estimate is 788. Counted again when the tool definitions change. Method.
Repository
https://github.com/mrfentmen/adobe-premiere-mcp
Registry
active, updated 2026-09-21 · registry entry
Changes
2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.87×.

Tool≈ Claude tokenso200k estimateShare of this server
create_sequence25913918 %
export_media19810613 %
apply_effect1759412 %
run_custom_script134729 %
import_media129699 %

Compare this server with others.

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

Servers that mention premiere.

History

We add a row when the result changes. A server with no change keeps its last row.

ProbedResultInitToolsClaudeo200k
2026-10-27 06:57alive303 ms111.5k788
2026-10-20 06:44alive301 ms11788

Badge for the README

mcpcost: alive

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher