Enterprise-grade Model Context Protocol (MCP) 서버가 전체를 노출합니다. DaVinci는 API를 AI 조수에 해결합니다. 이 프로젝트는 davinci-resolve-mcp 프로젝트 @samuelgursky에 의해, 이제는 현저하게 다른 건축입니다.

현대 MCP 명세를 지원하는 어떤 AI 체계도 호환이 되는.

---

그것이 작동하는 방법

대부분의 MCP 서버 하치장 모든 사용 가능한 도구로 AI의 컨텍스트 창에 세션 시작. 큰 API 표면으로 수백 가지 도구 정의를 의미합니다. 현재 작업이 필요한지 여부 또는로드 — 토큰과 느린 낭비 응답 시간.

이 서버는 kernel + domain 아키텍처를 사용합니다.

-Kernel 도구 (사용 가능, 총 6개): activate_domain, deactivate_domain, list_domains], get_version], get_current_page, switch_page. 이것은 당신이 해결하는 것에 관계없이 유용합니다.

• Domain 도구 ( 수요에로드 됨) : 전체 해결 API가 구성됩니다. 도메인 - 프로젝트 관리, 타임 라인 운영, 미디어 풀, 그리고 더. 이름 * activate_domain("project_management") 및 서버는 불을 notifications/tools/list_changed] 이벤트; MCP 클라이언트는 도구를 refetches

DaVinci MCP Professional

An enterprise-grade Model Context Protocol (MCP) server that exposes the full DaVinci Resolve scripting API to AI assistants. This project was inspired by the davinci-resolve-mcp project by @samuelgursky, even though it is now a significantly different architecture.

Compatible with any AI system that supports modern MCP specifications.

---

How It Works

Most MCP servers dump every available tool into the AI’s context window at session start. With a large API surface, that means hundreds of tool definitions loaded whether or not the current task needs them — wasting tokens and slowing response time.

This server uses a kernel + domain architecture instead:

• Kernel tools (always available, 6 total): activate_domain, deactivate_domain, list_domains, get_version, get_current_page, switch_page. These are useful regardless of what you’re doing in Resolve.
• Domain tools (loaded on demand): the full Resolve API is organized into domains — Project Management, Timeline Operations, Media Pool, and more. Call activate_domain("project_management") and the server fires a notifications/tools/list_changed event; your MCP client refetches the tool list and the domain’s tools are immediately available, no session restart needed.

Context cost at session start is bounded by the kernel alone. You expand it deliberately, only for the domains your current workflow actually needs.

---

Who This Is For

This server is built for independent creators and boutique studios where AI API costs are real and context overhead matters.

Compared to other popular MCP servers for DaVinci Resolve:

Most alternatives load every available tool definition into the AI’s context at session start. For a well-resourced production environment — a studio running Claude on dedicated infrastructure with token budgets absorbed into overhead — that approach is solid and the dense tool coverage is immediately useful.

This server makes a different architectural choice: 6 kernel tools at session start, domains activated on demand, context cost proportional to the work at hand. The full API surface (289 tools across 9 domains) is available, but none of it loads until you ask for it.

If you’re an independent creator or a small shop where every Claude API call has a cost, this architecture was designed for you. Professional-grade Resolve integration without professional-budget infrastructure requirements.

---

Prerequisites

• DaVinci Resolve Studio installed and licensed (the free edition does not support external scripting)
• Python 3.10 or later, installed system-wide via the