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-delivery)<a href="https://agentmods.dev/rules/samuelgursky/davinci-resolve-mcp/resolve-delivery"><img src="https://agentmods.dev/badge/rules/samuelgursky/davinci-resolve-mcp/resolve-delivery/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-delivery"><img src="https://agentmods.dev/badge/rules/samuelgursky/davinci-resolve-mcp/resolve-delivery.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.00054 | $0.00386 |
| Opus 5 | $0.00027 | $0.00193 |
| Sonnet 5 | $0.00011 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
resolve-delivery 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- resolve-delivery — 100% identical, 2 lines differ
What it actually says
Resolve Delivery / Deliverable QC work. Apply when: preparing render jobs, validating render settings, QCing a finished render vs spec, building render manifests, expanding texted/textless/stems deliverables, verifying media ingest, or producing a provenance/episode report.
Two servers — compute offline, apply live:
- Live (running Resolve,
davinci-resolve): render (probe_render_matrix, validate_render_settings, safe_set_render_settings, prepare_render_job, safe_quick_export), render_presets - Offline (.drp/.drt/.drx + DB, no Resolve,
davinci-resolve-advanced): deliverable (deliverable_qc, loudness_qc, reframe_blanking_check, conform_completeness, render_manifest, expand_deliverable), media (ingest_verify, media_inventory, sync, rename_plan), provenance (grade_provenance, cdl_export, episode_report) - Key rule: Deliverable QC is report-only: gate=review, never auto-pass-clear — surface per-field verdicts to a human. QC tools refuse rather than fabricate. deliverable/media QC needs ffmpeg+ffprobe on PATH. Render probes touch only synthetic fixtures.
Depth: docs/kernels/render-deliver-kernel.md. On-demand in any MCP client: the /delivery_workflow slash prompt. Portable skill: resolve-delivery in .agents/skills/. Never modify/transcode/derive source media (AGENTS.md).
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.
- 7d ago Changed a2d96fcecab2
- 9d ago First seen · 16 lines · 54 tokens per session scan A de8efe2c471f
resolve-delivery is a cursor rule published in the GitHub repository samuelgursky/davinci-resolve-mcp (2,568 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 386 once invoked, about $0.0003 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
livkiet-plugins-playai
Agent Framework plugin for voice synthesis with PlayAI API.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.