Video MCP Server

Video MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Animated b-roll overlays for short-form video. Paste a script, get an mp4. Free, MIT, local.

What you get

Make b-roll for your videos. Tell an agent what you want. Get an MP4 back.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

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

• Field — Type
• durationFrames — int
• fps — int
• width — int
• height — int
• theme — "light" \
• background — string
• backgroundImage — object
• palette — object
• tracks — Track[]
• kind — enum
• startFrame — int

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Video.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the video mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Video's toolset — Field, durationFrames, fps and 11 more — is a fair guide to whether it matches your workflow. It is maintained by alichherawalla; worth a glance at recent repository activity before you build anything load-bearing on it.

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