Kinocut MCP Server

Guardrailed video editing for AI agents: FFmpeg, captions, effects, Hyperframes, and receipts. Exposed over MCP by the kinocut mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Local-first FFmpeg tools, Video Receipts, quality gates, Hyperframes, and Shorts/Reels repurposing — for Claude Code, Cursor, and any MCP client. Free, Apache-2.0. Formerly mcp-video.

• Repurposing with receipts — — one recording → captioned Shorts/Reels/TikTok packages with manifests and review artifacts
• Podcast and interview cuts — — strongest segment, audio normalize, chapters, export
• Agent-driven media in CI — — repeatable edits from Claude Code, Cursor, Codex-style clients, or scripts

Its toolset

Everything the assistant can do here goes through one of these:

• Agent — driven media in CI** — repeatable edits from Claude Code, Cursor, Codex-style clients, or scripts
• Surface — Tip

Configuration

You will need one environment variable: GOLDEN_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Kinocut's toolset — Agent, Surface — is a fair guide to whether it matches your workflow. It is maintained by KyaniteLabs; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Kinocut's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the kinocut mcp server does with a few real requests.