Plugged.in Proxy vs MCP for Adobe Premiere Pro
Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). MCP for Adobe Premiere Pro is an MCP server published by leancoderkavy. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Plugged.in Proxy |  MCP for Adobe Premiere Pro |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b7c32590b270 Forks (GitHub): 30 Pulls (Docker Hub): 36 055 Stars (Docker Hub): 3 Stars (GitHub): 137 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.25.0 Downloads/month (npm): 18 294 Downloads/week (npm): 2 827 Forks (GitHub): 80 Stars (GitHub): 432 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.25.0 Downloads/month (npm): 18 294 Downloads/week (npm): 2 827 Forks (GitHub): 80 Stars (GitHub): 432 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Plugged.in Proxy | MCP for Adobe Premiere Pro |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 137 (worse) | 432 (better) |
| Pulls (Docker Hub) (differs) | 36 055 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 30 (worse) | 80 (better) |
| Last release (differs) | Not published | 2026-10-24 |
| Where it runs (differs) | On your machine (mcp/pluggedin-mcp-proxy) | On your machine (premiere-pro-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 3 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/veriteknik/pluggedin-mcp-proxy | github.com/leancoderkavy/premiere-pro-mcp |
| Changes in the last 7 days (differs) | 0 | 15 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Plugged.in Proxy
A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP servers from a single connection point with RAG capabilities and real-time notifications.
MCP for Adobe Premiere Pro
Local-first MCP for supported Adobe Premiere Pro workflows; start with a read-only connection check.
How to run each
Plugged.in Proxy As a local MCP server: Docker image
claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxyRequires: PLUGGEDIN_API_KEY (secret)
MCP for Adobe Premiere Pro As a local MCP server: npm package
claude mcp add --transport stdio premiere-pro -- npx -y premiere-pro-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of MCP for Adobe Premiere Pro publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of MCP for Adobe Premiere Pro publish no settings it asks for, so we do not compare settings.
What it can do: Plugged.in Proxy · What it can do: MCP for Adobe Premiere Pro · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.