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/ayushozha/AdobePremiereProMCPWrote 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/ayushozha/adobepremierepromcp/premierpro-mcp)<a href="https://agentmods.dev/mcp/ayushozha/adobepremierepromcp/premierpro-mcp"><img src="https://agentmods.dev/badge/mcp/ayushozha/adobepremierepromcp/premierpro-mcp/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/ayushozha/adobepremierepromcp/premierpro-mcp"><img src="https://agentmods.dev/badge/mcp/ayushozha/adobepremierepromcp/premierpro-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
premierpro-mcp 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 11d 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
{
"premierpro-mcp": {
"type": "stdio",
"command": "./go-orchestrator/bin/premierpro-mcp",
"args": [
"--log-level",
"error"
],
"env": {}
}
}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.
- 11d ago First seen · 11 lines scan A b34b3bbdec11
premierpro-mcp is an MCP server published in the GitHub repository ayushozha/AdobePremiereProMCP (99 stars, last pushed 11d 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
premiere-pro
MCP Bridge for Adobe Premiere Pro with 283 tools for AI-driven video editing. Runs locally from the adobe-premiere-pro-mcp npm package.
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.
mcp-indesign
MCP server for Adobe InDesign automation on Windows. Runs locally from the mcp-indesign npm package.
adobe-firefly-mcp
Local MCP server that drives Adobe Firefly through a persistent Playwright browser session. Runs locally from the adobe-firefly-mcp npm package.
frameio-agent
MCP server "frameio-agent" as configured in vaxastudio/frameio-agent. Runs locally from the frameio-agent Python package.
photoshop-mcp-windows-first
MCP server "photoshop-mcp-windows-first" as configured in Vaxaxas/photoshop-mcp-windows-first. Runs locally from the photoshop-mcp-windows-first npm package.