<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: 이영준 (leesam)</title>
    <description>The latest articles on DEV Community by 이영준 (leesam) (@_leesam_ded8ba7b9a7e).</description>
    <link>https://dev.to/_leesam_ded8ba7b9a7e</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4086336%2Fa1d41299-2dd2-410b-b942-86b774d8c489.jpeg</url>
      <title>DEV Community: 이영준 (leesam)</title>
      <link>https://dev.to/_leesam_ded8ba7b9a7e</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/_leesam_ded8ba7b9a7e"/>
    <language>en</language>
    <item>
      <title>Driving DaVinci Resolve's Free Edition with Claude, From Inside the App</title>
      <dc:creator>이영준 (leesam)</dc:creator>
      <pubDate>Thu, 20 Aug 2026 09:11:47 +0000</pubDate>
      <link>https://dev.to/_leesam_ded8ba7b9a7e/driving-davinci-resolves-free-edition-with-claude-from-inside-the-app-4h19</link>
      <guid>https://dev.to/_leesam_ded8ba7b9a7e/driving-davinci-resolves-free-edition-with-claude-from-inside-the-app-4h19</guid>
      <description>&lt;p&gt;&lt;strong&gt;The wall&lt;/strong&gt;&lt;br&gt;
Every MCP server that controls DaVinci Resolve connects to it the same way: a script running outside the app calls into Resolve's scripting API over the network. That works fine on Resolve Studio. On the free edition it doesn't work at all — Lite is sandboxed and blocks any script that isn't launched from inside Resolve itself.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The one door left open&lt;/strong&gt;&lt;br&gt;
Free Resolve still runs Python scripts launched from its own Workspace &amp;gt; Scripts menu. A menu script gets the resolve object injected for free, can run a long-lived loop, and — because the sandboxed app ships the com.apple.security.network.server entitlement — can open a localhost listening socket. That's the whole trick: the MCP server is the menu script.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Claude Code ──HTTP JSON-RPC (MCP)──▶  127.0.0.1:8765/mcp
                                          │   server runs INSIDE Resolve
                                          │   (Workspace &amp;gt; Scripts &amp;gt; Utility)
                                          ▼
                              command queue → main script thread
                                          ▼
                              global `resolve` object → Resolve API
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;What it gets you&lt;/strong&gt;&lt;br&gt;
157 tools across editing, color, render, media pool, and Fusion title styling — driven from plain-language requests in Claude Code. Zero dependencies: pure Python standard library, so there's nothing to pip install into Resolve's bundled interpreter.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Try it&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone https://github.com/2sem/davinci-resolve-lite-mcp.git
&lt;span class="nb"&gt;cd &lt;/span&gt;davinci-resolve-lite-mcp
./install.sh
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;macOS only for now. Full tools reference and demo video in the repo.&lt;/p&gt;

</description>
      <category>api</category>
      <category>claude</category>
      <category>mcp</category>
      <category>python</category>
    </item>
  </channel>
</rss>
