davinci-resolve-mcp is an MCP server that lets AI assistants control DaVinci Resolve Studio through its scripting API, including editing, media organization, rendering, grading, and other project tasks. It is for users who want agents to operate Resolve and inspect media through a local control panel. The catalogue entries support agent workflows for this Resolve integration.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/samuelgursky/davinci-resolve-mcpWrote 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.
[](https://agentmods.dev/rules/samuelgursky/davinci-resolve-mcp/resolve-repo)<a href="https://agentmods.dev/rules/samuelgursky/davinci-resolve-mcp/resolve-repo"><img src="https://agentmods.dev/badge/rules/samuelgursky/davinci-resolve-mcp/resolve-repo/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/samuelgursky/davinci-resolve-mcp/resolve-repo"><img src="https://agentmods.dev/badge/rules/samuelgursky/davinci-resolve-mcp/resolve-repo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00221 | $0.00221 |
| Opus 5 | $0.00111 | $0.00111 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
resolve-repo 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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- resolve-repo — 94% identical, 2 lines differ
What it actually says
This is the DaVinci Resolve MCP server: a Python MCP server (37 compound tools, 384 granular in --full mode) driving Resolve via its scripting API, plus an offline Node "advanced" server (18 tools) that authors .drp/.drt/.drx files and patches the project DB with no Resolve running. Kernel coverage: 136 guarded workflow actions.
- Canonical agent brief: AGENTS.md. Operating reference: docs/SKILL.md. Per-action depth: docs/kernels/*. Advanced (offline) catalog: resolve-advanced/README.md.
- Never modify, transcode, convert, proxy, relink, or create derivatives of source media unless explicitly asked. Analysis output goes to sidecars/scratch/the analysis project root.
- Do not duplicate version numbers, tool counts, or kernel-action counts into prose — they drift. Reference the docs above.
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.
- today Changed c095b0671433
- yesterday Changed 4784345f0a87
- 2d ago Changed b44cc240fd30
- 12d ago First seen · 13 lines · 221 tokens per session scan A 60dc86731c3f
resolve-repo is a cursor rule published in the GitHub repository samuelgursky/davinci-resolve-mcp (2,701 stars, last pushed today), licensed MIT. It adds 221 tokens to every session, about $0.0011 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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.