MCP servers · airta-admin

DaVinci Resolve Local Bridge MCP

An MCP server that gives AI assistants controlled access to DaVinci Resolve through 218 auto-discovered tools.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

This MCP server lets AI assistants control DaVinci Resolve. A bridge script runs inside Resolve's own process and exposes the Resolve scripting API, including on the Free edition, which otherwise blocks external scripting. The MCP server runs as a separate process and forwards tool calls to the bridge over localhost HTTP. It discovers the bridge's 218 actions automatically and exposes each one as a tool with a resolve_ prefix, covering projects, timelines, media, Fusion, color grading, rendering and supported optional extensions.

It suits anyone who wants an assistant to carry out Resolve tasks, such as checking the connection, creating a project with set resolution and frame rate, adding a timeline, switching pages or managing presets. It is designed for MCP-compatible assistants, and the publisher documents setup for Claude Desktop, Cursor, Devin, Claude Code and generic MCP clients.

Setup involves running the installer, which adds a launcher under Workspace > Workflow Integrations, then restarting Resolve once. The MCP server's Python dependencies are installed separately, and the server is added to the assistant's configuration using stdio transport. Each session, the bridge is started from the Workflow Integrations panel, and the panel should report that it is running on localhost port 8787 with 218 actions.

Limitations and requirements

Requires DaVinci Resolve 18.5 or later (Free or Studio) and Python 3.10 or later. An MCP-compatible AI assistant is needed. The bridge must be running inside Resolve, started from the Workflow Integrations panel, before the assistant can use the tools. The MCP server and bridge communicate over localhost HTTP on the same machine.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    DaVinci Resolve Local Bridge MCP

    Control DaVinci Resolve from any AI assistant. 215 MCP tools covering the full Resolve API.

    v1.0.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
awslabs

MCP servers for AWS (AWS Labs)

A large open-source collection of MCP servers from AWS Labs for building and operating on AWS: documentation, infrastructure, databases, AI services, cost and more.

9.9K GitHub starsCloud & DevOpsData & databases
Updated 17 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 17 Nov 2026
MCP servers
docker

Docker Hub MCP Server

Docker's MCP server that helps an AI assistant find and compare container images on Docker Hub and, with your token, manage your own repositories and tags.

171 GitHub starsCloud & DevOpsSoftware development
Updated 13 Nov 2026
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026