Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/hetpatel-11/Adobe_Premiere_Pro_MCPWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/hetpatel-11/adobe_premiere_pro_mcp/premiere-pro-mcp-premiere-pro)<a href="https://agentmods.dev/mcp/hetpatel-11/adobe_premiere_pro_mcp/premiere-pro-mcp-premiere-pro"><img src="https://agentmods.dev/badge/mcp/hetpatel-11/adobe_premiere_pro_mcp/premiere-pro-mcp-premiere-pro/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/hetpatel-11/adobe_premiere_pro_mcp/premiere-pro-mcp-premiere-pro"><img src="https://agentmods.dev/badge/mcp/hetpatel-11/adobe_premiere_pro_mcp/premiere-pro-mcp-premiere-pro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
premiere-pro scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"premiere-pro": {
"command": "npx",
"args": [
"-y",
"adobe-premiere-pro-mcp@latest"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 9 lines scan A 7cec6375a779
premiere-pro is an MCP server published in the GitHub repository hetpatel-11/Adobe_Premiere_Pro_MCP (541 stars, last pushed 8d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
premierpro-mcp
MCP server "premierpro-mcp" as configured in ayushozha/AdobePremiereProMCP. Launched with ./go-orchestrator/bin/premierpro-mcp --log-level error.
photoshop-mcp
MCP server for Adobe Photoshop — 102 tools (generative AI + recipes), standalone web UI. Control Ph… Runs locally from the @alisaitteke/photoshop-mcp npm package.
adobe-analytics
MCP server "adobe-analytics", hosted remotely at aa-mcp.adobe.io, as configured in adobe/skills.
premiere-pro
MCP server for Adobe Premiere Pro with 321 core AI video editing tools and a capability-aware UXP bridge for supported Premiere workflows. Runs locally from the premiere-pro-mcp npm package.
cassette
MCP server "cassette" as configured in Cassette-Editor/oh-my-cassette. Runs ${CLAUDE_PROJECT_DIR:-.}/scripts/run_local_mcp.py with python3. Needs 1 environment variable to run.
after-effects
Control Adobe After Effects with AI — describe the animation you want and it gets built: layers, keyframes, effects, expressions and text, all editable afterwards. Runs locally from the @engine-room/after-effects-mcp npm package.