resolve-mcp: Instructions file for Claude Code

CLAUDE.md

resolve-mcp CLAUDE.md is an instructions file for Claude Code from jenkinsm13/resolve-mcp. It costs 2,227 tokens per session, scanned A, original, MIT.

An MCP server that exposes DaVinci Resolve's video-editing controls to coding agents, along with some Google Gemini-based tools.

In plain words
What is it for?
Use it to work with Resolve projects, timelines, bins, and render queues, call Resolve scripting actions, read project information, and use the optional AI bridge tools.
Why use it?
It lets an agent automate and inspect Resolve projects through a large collection of scripting tools instead of writing each integration from scratch.

Instructions file for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: mentions subagents.

This is jenkinsm13/resolve-mcp's own configuration. It tells Claude Code how to work on resolve-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything resolve-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jenkinsm13/resolve-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jenkinsm13/resolve-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/jenkinsm13/resolve-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for resolve-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jenkinsm13/resolve-mcp/claude-md.svg)](https://agentmods.dev/instructions/jenkinsm13/resolve-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/jenkinsm13/resolve-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/jenkinsm13/resolve-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,227 This file is loaded in full into every session.
When invoked 2,227 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.02227 $0.02227
Opus 5 $0.01113 $0.01113
Sonnet 5 $0.00445 $0.00445
Haiku 4.5 $0.00223 $0.00223

Measured 6d ago against content hash 54bb6f978e78, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

resolve-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

resolve-mcp

MCP server exposing ~296 tools for the DaVinci Resolve scripting API (v20.3), plus AI bridge tools powered by Google Gemini.

Quick Start

pip install -e ".[dev]"         # install package + ruff/pytest/pyright
cp .env.example .env            # optional — only needed for AI bridge tools
resolve-mcp                     # run the MCP server (needs Resolve open)
pytest tests/ -v                # run tests (no Resolve needed)

Architecture

  • Package: resolve_mcp/ — all modules use relative imports (from .config import mcp)
  • Entry point: resolve_mcp/__init__.pymain()mcp.run()
  • Tool registration: Every tool module is imported in __init__.py. The @mcp.tool decorator on each function auto-registers it with the FastMCP server.
  • MCP resources: resources.py exposes read-only resolve:// URIs (project, timelines, bins, render-queue, version)

Key Patterns

Adding a new tool

  1. Create or edit a *_tools.py module
  2. Import from .config import mcp and from .resolve import get_resolve, _boilerplate
  3. Decorate with @mcp.tool
  4. If the module is new, add from . import my_new_tools in __init__.py

Gotcha — cascading imports: 18 modules are loaded indirectly through import chains rather than __init__.py. For example, edit_tools.py imports clip_edit_tools, which imports clip_query_tools. If you add tools to one of these indirect modules, they'll register correctly without touching __init__.py — but only because the parent module already imports them. See tests/test_conventions.py::INDIRECT_IMPORT_MODULES for the full list.

Resolve connection

  • get_resolve() returns the Resolve scripting object (or None if not running)
  • _boilerplate() returns (resolve, project, media_pool) — a 3-tuple, no timeline. Get timeline separately: project.GetCurrentTimeline()
  • All Resolve API calls go through the network scripting interface

Error handling

  • @safe_resolve_call decorator in errors.py wraps tools to catch exceptions and return MCP-friendly error strings — including your own bugs (NameError, KeyError, etc.), which become silent string returns instead of tracebacks
  • Custom exception classes: ResolveNotRunning, ProjectNotOpen, TimelineNotFound, BinNotFound, ClipNotFound, ItemNotFound, StudioRequired

Read the full file on GitHub · 139 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 139 lines · 2,227 tokens per session scan A 54bb6f978e78

Subscribe to this mod's changes

resolve-mcp CLAUDE.md is an instructions file published in the GitHub repository jenkinsm13/resolve-mcp (6 stars, last pushed 4mo ago), licensed MIT. It adds 2,227 tokens to every session, about $0.0111 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens