Сервер Model Context Protocol (MCP) корпоративного уровня, который предоставляет полную информацию DaVinci Resolve скриптинг API для помощников ИИ. Этот проект был вдохновлен Проект davinci-resolve-mcp @samuelgursky, хотя сейчас это значительно другая архитектура.

Совместим с любой системой ИИ, поддерживающей современные спецификации MCP.

Как это работает

Большинство MCP-серверов сбрасывают все доступные инструменты в контекстное окно ИИ. Начинается сеанс. С большой поверхностью API это означает сотни определений инструментов. загружается независимо от того, нужна ли им текущая задача — растрачивание токенов и замедление Время отклика.

Этот сервер использует архитектуру kernel + domain:

• ** Инструменты ядра** (всегда доступны, всего 6): activate_domain, [[Т1]], [[Т2]], [[Т3], [[Т4]], [[Т5]]. Они полезны независимо от того, что вы делаете в Resolve. ** Инструменты домена** (загружены по требованию): полный API Resolve организован в домены — управление проектами, операции по временной шкале, медиа-пул и многое другое. Звони. [[Т6]] и сервер запускает notifications/tools/list_changed событие; ваш MCP-клиент восстанавливает инструмент

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