DaVinci Resolve MCP vs Glif
DaVinci Resolve MCP is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
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. Glif is an MCP server published by glif.app. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). As of our marketplace pass on 2026-11-12. 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 |   Glif | |
|---|---|---|
| Community marketplace ciprianspiridon/davinci-resolve-mcp | Removed on 2026-10-20 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 32 Stars (GitHub): 217 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:3f93ddceeb99 Forks (GitHub): 32 Pulls (Docker Hub): 20 329 Stars (Docker Hub): 2 Stars (GitHub): 217 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 | DaVinci Resolve MCPno longer listed · | Glif |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 3 |
| Stars (GitHub) (differs) | 5 | 217 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 20 329 |
| Forks (GitHub) (differs) | 0 | 32 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 10 |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 5 | 11 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/ciprianspiridon/davinci-resolve-mcp | github.com/glifxyz/glif-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 1 h ago |
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.
-
DaVinci Resolve MCP (free edition)
Control DaVinci Resolve 21.1 (free edition included) from Claude via a Lua bridge. See README.
-
Control DaVinci Resolve, including the free Lite edition. Manual setup only — see README.
-
Typed, safe MCP server for DaVinci Resolve: every write verified, deletes confirmed, snapshots.
-
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.
-
Surehand MCP for Adobe After Effects
Your AI works in Adobe After Effects and proves what it did: change reports, pixel proofs, QC.
What each says it does
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.
Glif
Generate images, video, and audio with Glif's media-generation agent
How to run each
DaVinci Resolve MCP
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Glif As a remote MCP server
claude mcp add --transport http glif https://glif.app/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Glif has a remote endpoint we check. How we check endpoints
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 DaVinci Resolve MCP asks for
RESOLVE_MCP_LOG_LEVEL
Only Glif asks for
GLIF_API_TOKEN (secret)GLIF_IDSIGNORE_SAVED_GLIFS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: DaVinci Resolve MCP · What it can do: Glif · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.