DaVinci Resolve Lua MCP vs MCP for Adobe Premiere Pro
A side-by-side look at the DaVinci Resolve Lua MCP and MCP for Adobe Premiere Pro MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose DaVinci Resolve Lua MCP for multimedia process work; choose MCP for Adobe Premiere Pro for multimedia process as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose DaVinci Resolve Lua MCP when
- You need dedicated capabilities in the Multimedia Process domain.
- You want tools like
resolve_status, run_lua, get_project_info.
Choose MCP for Adobe Premiere Pro when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_project_info, get_active_sequence, list_project_items.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 47/100 · Fair | 64/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 401 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 15 | 80 |
| Full listing | View DaVinci Resolve Lua MCP | View MCP for Adobe Premiere Pro |
Tools & capabilities
DaVinci Resolve Lua MCP tools 15
resolve_statusWhether the bridge is running and why not, its session, the platform, the self-install outcome and, when alive, product, version, edition, page and projectrun_luaRuns a Lua 5.1 chunk inside Resolve with the live `resolve` object; returns its first return value as JSON plus captured prints and errorsget_project_infoName, page, database, frame rate, resolution, timeline count, root-bin counts and the current timeline of the open projectlist_projectsProjects in the current project-manager folder with dates and notes; marks the open onelist_timelinesEvery timeline with unique id, frame range and track counts; marks the current onelist_media_pool_clipsClips in one bin with path, duration, fps, resolution, type, frames and colourget_timeline_itemsItems on one track of the current timeline with type, frames, source frames, enabled state and file pathadd_markerAdds a marker to the current timeline and returns the stored markerdelete_markersDeletes every marker of one colour, or all markers, from the current timelineset_current_timelineMakes the named timeline current; an unknown name lists the known onesopen_projectLoads the named project, saving the open one first by default; an unknown name lists the known projectsrender_current_timelineQueues and starts a render of the current timeline and returns the job id- +3 more on the listing page
MCP for Adobe Premiere Pro tools 80
get_project_infoCurrent project name, path, sequences, itemsget_active_sequenceDetailed active sequence with all clipslist_project_itemsAll items in the project panelget_full_project_overviewComprehensive snapshot: bin tree, sequences, media typesget_full_sequence_infoExhaustive sequence data: tracks, clips, effects, markersget_full_clip_infoEverything about a clip: effects, keyframes, metadataget_timeline_summaryHuman-readable overview: duration, coverage %, effectssearch_project_itemsFilter by name, extension, offline status, color labelget_premiere_stateFull snapshot: project, sequence, playhead, selectioninspect_dom_objectExplore any Premiere Pro DOM object interactivelyget_advanced_feature_supportCollaboration/AI API support, prerequisites, entitlements, and user-assisted boundariescreate_editorial_planCreate a review-only local editorial plan from captured project context- +68 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
DaVinci Resolve Lua MCP
No confirmed install command for DaVinci Resolve Lua MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP for Adobe Premiere Pro
{
"mcpServers": {
"mcp-for-adobe-premiere-pro": {
"command": "npx",
"args": [
"-y",
"premiere-pro-mcp@1.24.0"
]
}
}
}
Frequently asked questions
DaVinci Resolve Lua MCP is categorized under Multimedia Process and uses an install path we have not confirmed yet. MCP for Adobe Premiere Pro belongs to Multimedia Process and uses a local stdio subprocess. Pick DaVinci Resolve Lua MCP for multimedia process work and MCP for Adobe Premiere Pro for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. DaVinci Resolve Lua MCP has no confirmed install command yet — follow its own setup instructions.
DaVinci Resolve Lua MCP has no declared pricing — check the project's own site. MCP for Adobe Premiere Pro has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add davinci-resolve-lua-mcp and mcp-for-adobe-premiere-pro as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DaVinci Resolve Lua MCP has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 4 GitHub stars. MCP for Adobe Premiere Pro has 64/100 (Good) with 0 views, 0 installs and 401 GitHub stars.