davinci-resolve-mcp 2.211.0 → 2.212.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,40 @@
2
2
 
3
3
  Release history for the DaVinci Resolve MCP Server. The latest release is summarized in the root README; older entries live here to keep the README focused.
4
4
 
5
+ ## What's New in v2.212.0 — graph risk follows the graph the call targets
6
+
7
+ ### Changed
8
+
9
+ - **Every `graph` mutation now reports the blast radius of its `source`.**
10
+ The graph tool resolves `source` as `"timeline"` (the DEFAULT, the
11
+ timeline-level node graph), `"item"` (one clip), or
12
+ `"color_group_pre"`/`"color_group_post"` (a group's shared graph), and every
13
+ mutation lands on whichever graph that names. The classifier reported all
14
+ five graph actions as item-scoped regardless, so `reset_all_grades` on a
15
+ color-group graph — which wipes the grade of every clip in the group — read
16
+ as one item. The radius is now derived from the call: timeline, item, or
17
+ project for a color group, and the reasons name the target graph.
18
+
19
+ - **`graph.set_lut` and `graph.apply_arri_cdl_lut` are HIGH on the timeline or a color-group graph, MEDIUM on one item.**
20
+ A plain `set_lut` call with no `source` restyles every clip on the timeline;
21
+ rating that MEDIUM under-stated it, while rating the item-scoped call HIGH
22
+ would over-block a one-clip LUT. Safe mode now blocks the broad cases
23
+ unless `allow_risky_operation=true`; the item case passes as before.
24
+ `reset_all_grades` and `apply_grade_from_drx` stay HIGH, `set_node_enabled`
25
+ stays LOW — only their reported scope changed.
26
+
27
+ ### Added
28
+
29
+ - Tests: safe mode blocks broad LUT writes before the handler and allows
30
+ item-scoped ones; the classifier's LUT split; the radius of every graph
31
+ action across all five source values; and a medium-band matrix pinning
32
+ every remaining MEDIUM destructive action as recognised, destructive, not
33
+ confirmation-gated, and carrying its reviewed radius.
34
+
35
+ - Adapted from PR #192 by @Rohitkanithi, which introduced the scope split
36
+ and its tests for the two LUT actions; landed with the radius generalised
37
+ to every graph action, since the same `source` governs them all.
38
+
5
39
  ## What's New in v2.211.0 — dry_run on an action that cannot honour it now refuses instead of executing
6
40
 
7
41
  ### Changed
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  English | [简体中文](README.zh-CN.md)
4
4
 
5
- [![Version](https://img.shields.io/badge/version-2.211.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
5
+ [![Version](https://img.shields.io/badge/version-2.212.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
6
6
  [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
7
7
  [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
8
8
  [![Tools](https://img.shields.io/badge/MCP%20Tools-36%20(353%20full)-blue.svg)](#server-modes)
package/README.zh-CN.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  [English](README.md) | 简体中文
4
4
 
5
- [![Version](https://img.shields.io/badge/version-2.211.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
5
+ [![Version](https://img.shields.io/badge/version-2.212.0-blue.svg)](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
6
6
  [![npm](https://img.shields.io/npm/v/davinci-resolve-mcp.svg?label=npm&color=CB3837)](https://www.npmjs.com/package/davinci-resolve-mcp)
7
7
  [![API Coverage](https://img.shields.io/badge/API%20Coverage-100%25-brightgreen.svg)](docs/reference/api-coverage.md)
8
8
  [![Tools](https://img.shields.io/badge/MCP%20Tools-36%20(353%20full)-blue.svg)](#服务器模式)
@@ -12,7 +12,7 @@
12
12
  [![Python](https://img.shields.io/badge/python-3.10+-green.svg)](https://www.python.org/downloads/)
13
13
  [![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
14
14
 
15
- > 本翻译对应 v2.211.0 版 README。如与英文原版有出入,以 [英文原版](README.md) 为准。
15
+ > 本翻译对应 v2.212.0 版 README。如与英文原版有出入,以 [英文原版](README.md) 为准。
16
16
 
17
17
  一个 Model Context Protocol (MCP) 服务器,让 AI 助手通过官方脚本 API 控制 DaVinci Resolve Studio(达芬奇)。它提供完整的 API 覆盖,外加带护栏的工作流助手,涵盖剪辑、媒体池整理、渲染设置、审阅标记、调色、Fusion、Fairlight、项目生命周期任务、扩展开发,以及不碰源媒体的媒体分析。
18
18
 
package/install.py CHANGED
@@ -37,7 +37,7 @@ from src.utils.update_check import (
37
37
 
38
38
  # ─── Version ──────────────────────────────────────────────────────────────────
39
39
 
40
- VERSION = "2.211.0"
40
+ VERSION = "2.212.0"
41
41
  # Only hard floor: mcp[cli] requires Python 3.10+. There is no upper bound —
42
42
  # Resolve's scripting bridge loads into newer interpreters on recent builds
43
43
  # (Python 3.14 verified against Resolve Studio 20.3.2). Older Resolve builds
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "davinci-resolve-mcp",
3
- "version": "2.211.0",
3
+ "version": "2.212.0",
4
4
  "description": "NPM bootstrapper for the DaVinci Resolve MCP Server.",
5
5
  "license": "MIT",
6
6
  "author": "Samuel Gursky <samgursky@gmail.com>",
@@ -87,7 +87,7 @@ if not logging.getLogger().handlers:
87
87
  handlers=[logging.StreamHandler()],
88
88
  )
89
89
 
90
- VERSION = "2.211.0"
90
+ VERSION = "2.212.0"
91
91
  logger = logging.getLogger("davinci-resolve-mcp")
92
92
  logger.info(f"Starting DaVinci Resolve MCP Server v{VERSION}")
93
93
  logger.info(f"Detected platform: {get_platform()}")
package/src/server.py CHANGED
@@ -11,7 +11,7 @@ Usage:
11
11
  python src/server.py --full # Start the 353-tool granular server instead
12
12
  """
13
13
 
14
- VERSION = "2.211.0"
14
+ VERSION = "2.212.0"
15
15
 
16
16
  import base64
17
17
  import os
@@ -287,13 +287,42 @@ class RiskClassificationHook(LifecycleHook):
287
287
  ("timeline_item_color", "smart_reframe"),
288
288
  ("timeline_item_color", "create_magic_mask"),
289
289
  ("timeline_item_color", "regenerate_magic_mask"),
290
- ("graph", "set_lut"),
291
- ("graph", "apply_arri_cdl_lut"),
292
290
  # Importing or switching the active comp changes what renders.
293
291
  ("timeline_item_fusion", "import_comp"),
294
292
  ("timeline_item_fusion", "load_comp"),
295
293
  }
296
294
 
295
+ #: Raw graph LUT writes. Their level follows the graph they target (see
296
+ #: `_graph_scope`): MEDIUM on one item, HIGH on the timeline graph (the
297
+ #: tool's DEFAULT) or a color-group graph, where one call restyles every
298
+ #: clip on the timeline or in the group. Adapted from PR #192.
299
+ _GRAPH_LUT_ACTIONS: Set[Tuple[str, str]] = {
300
+ ("graph", "set_lut"),
301
+ ("graph", "apply_arri_cdl_lut"),
302
+ }
303
+
304
+ @staticmethod
305
+ def _graph_scope(params: Dict[str, Any]) -> Tuple["BlastRadius", str]:
306
+ """Blast radius of a `graph` tool call, from its `source` param.
307
+
308
+ The graph tool resolves `source` as "timeline" (default) ->
309
+ Timeline.GetNodeGraph(), "item" -> TimelineItem.GetNodeGraph(), and
310
+ "color_group_pre"/"color_group_post" -> the group's pre/post clip
311
+ graph. Every graph mutation — LUT, DRX apply, reset, node toggle —
312
+ lands on whichever graph that names, so the scope is a property of
313
+ the call, not of the action, and a rating that says "item" for a
314
+ reset of a color-group graph is wrong by the size of the group.
315
+ """
316
+ source = str(params.get("source") or "timeline")
317
+ if source == "item":
318
+ return BlastRadius.ITEM, "one timeline item's graph"
319
+ if source in {"color_group_pre", "color_group_post"}:
320
+ return (
321
+ BlastRadius.PROJECT,
322
+ f"a color group's {source} graph (every clip in the group)",
323
+ )
324
+ return BlastRadius.TIMELINE, "the timeline node graph (every clip on the timeline)"
325
+
297
326
  _READ_ONLY_PREFIXES = ("get_", "list_", "query_", "probe_", "inspect_", "export_", "check_")
298
327
 
299
328
  @classmethod
@@ -319,14 +348,31 @@ class RiskClassificationHook(LifecycleHook):
319
348
  if params.get("ripple", False):
320
349
  radius = BlastRadius.TIMELINE
321
350
  reasons.append("Ripple mode alters downstream timeline synchronization")
351
+ elif tool_name == "graph":
352
+ radius, scope = cls._graph_scope(params)
353
+ reasons.append(f"Graph target: {scope}")
322
354
  else:
323
355
  radius = BlastRadius.ITEM
324
356
  conf_required = True
325
357
  reasons.append(f"Destructive timeline edit: {action}")
358
+ elif pair in cls._GRAPH_LUT_ACTIONS:
359
+ destructive = True
360
+ radius, scope = cls._graph_scope(params)
361
+ if radius is BlastRadius.ITEM:
362
+ level = RiskLevel.MEDIUM
363
+ reasons.append(f"Raw graph LUT write '{action}' is scoped to {scope}")
364
+ else:
365
+ level = RiskLevel.HIGH
366
+ conf_required = True
367
+ reasons.append(f"Raw graph LUT write '{action}' targets {scope}")
326
368
  elif pair in cls._LOW_RISK_ACTIONS:
327
369
  level = RiskLevel.LOW
328
370
  destructive = True
329
- radius = BlastRadius.ITEM
371
+ if tool_name == "graph":
372
+ radius, scope = cls._graph_scope(params)
373
+ reasons.append(f"Graph target: {scope}")
374
+ else:
375
+ radius = BlastRadius.ITEM
330
376
  reasons.append(f"Bounded reversible edit: {action}")
331
377
  elif pair in cls._MEDIUM_RISK_ACTIONS:
332
378
  level = RiskLevel.MEDIUM