DaVinci Resolve MCP Server

Created By
apvlva year ago
A Model Context Protocol (MCP) server for interacting with DaVinci Resolve and Fusion
Overview

What is DaVinci Resolve MCP Server?

DaVinci Resolve MCP Server is a Model Context Protocol (MCP) server designed for seamless interaction with DaVinci Resolve and Fusion, enabling AI assistants to control and manage projects within these applications.

How to use DaVinci Resolve MCP Server?

To use the server, install it in Claude Desktop or 5ire, connect to DaVinci Resolve, and utilize various commands to manage projects, timelines, and media.

Key features of DaVinci Resolve MCP Server?

  • Two-way communication with AI assistants like Claude.
  • Project management capabilities including creation and loading of projects.
  • Timeline manipulation for creating and modifying timelines.
  • Media management for organizing and importing media files.
  • Fusion integration for creating and modifying compositions.
  • Code execution for running Python scripts within DaVinci Resolve.

Use cases of DaVinci Resolve MCP Server?

  1. Automating video editing tasks using AI.
  2. Managing complex projects in DaVinci Resolve through voice commands.
  3. Integrating AI for enhanced media management and editing workflows.

FAQ from DaVinci Resolve MCP Server?

  • Can I use this server with any version of DaVinci Resolve?

It is recommended to use DaVinci Resolve Studio version 17 or higher.

  • Is there a specific AI assistant required to use this server?

Yes, it is designed to work with Claude Desktop or 5ire as AI clients.

  • What programming languages are supported for code execution?

The server supports Python and Lua for executing scripts.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
apvlv
Star
0
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago