Plugged.in Proxy vs DaVinci Resolve MCP
DaVinci Resolve MCP is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). DaVinci Resolve MCP is a plugin bundle for AI coding tools published by davinci-resolve-mcp contributors. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b7c32590b270 Forks (GitHub): 30 Pulls (Docker Hub): 35 901 Stars (Docker Hub): 3 Stars (GitHub): 136 Not marked · First seen |
Not listed |
| Community marketplace ciprianspiridon/davinci-resolve-mcp | Not listed | Removed on 2026-10-20 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 5 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 | DaVinci Resolve MCPno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 136 | 5 |
| Pulls (Docker Hub) (differs) | 35 901 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 30 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/pluggedin-mcp-proxy) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 1, secrets among them: 0 |
| Parts of the bundle (differs) | Not a bundle | 5 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/veriteknik/pluggedin-mcp-proxy | github.com/ciprianspiridon/davinci-resolve-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of DaVinci Resolve MCP
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Control DaVinci Resolve, including the free Lite edition. Manual setup only — see README.
-
DaVinci Resolve Local Bridge MCP
Control DaVinci Resolve from any AI assistant. 215 MCP tools covering the full Resolve API.
-
Control the free edition of DaVinci Resolve 21.1 from Claude through a Lua script inside Resolve.
-
Kdenlive video editing MCP - 36 tools for project, timeline, filters and melt rendering
-
Local-first MCP for supported Adobe Premiere Pro workflows; start with a read-only connection check.
-
Review-first stdio MCP for Movi: analyze, review, overlay edit, and dry-run preview.
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.
DaVinci Resolve MCP
Full-coverage MCP server for DaVinci Resolve Studio (editing, media pool, color grading, Fusion, Fairlight, AI/Neural Engine, rendering, local transcription — 316 live tools) plus 18 offline/advanced tools (.drx/.drt/.drp, CDL/LUT, project DB, provenance) that work without Resolve running. Bundles the davinci-resolve agent skill for onboarding and day-to-day operation.
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-proxy
Requires: PLUGGEDIN_API_KEY (secret)
DaVinci Resolve MCP
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of DaVinci Resolve MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only Plugged.in Proxy asks for
PLUGGEDIN_API_BASE_URLPLUGGEDIN_API_KEY (secret)
Only DaVinci Resolve MCP asks for
RESOLVE_MCP_LOG_LEVEL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Plugged.in Proxy · What it can do: DaVinci Resolve MCP · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.