MCP Video MCP Server

MCP Video MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Video directly instead of describing what you should do. 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.

What you get

• 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

Setting it up

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

What the assistant can call

Once MCP Video is connected, these are the calls the assistant has available:

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

Configuration and credentials

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.

Before you rely on it

• 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 mcp video mcp server does with a few real requests.

Choosing this one

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. MCP Video'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.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.