execute_ffmpegLABSCO SUMMARY
One tool that trades a memorised flag syntax for a sentence.
The whole point is not having to remember how to express a trim or a speed change in FFmpeg arguments; ask for it, and the progress reporting means a long transcode does not look like a hang. Because it runs FFmpeg commands the client composed, keep it pointed at working directories you are happy to have written to and read the command before approving anything destructive.
What it is
A Python MCP server that puts FFmpeg behind one tool. You describe the edit in plain language, the client turns it into an FFmpeg command, and the server validates it, runs it, and reports progress while it works.
What you get
execute_ffmpeg— takes a command string, validates it, runs it, and reports real-time progress- Every FFmpeg operation is in reach: trimming, merging, format conversion, speed changes, audio tracks in and out, subtitles and basic filters
- Detailed errors passed back to the client, so a malformed command becomes a correction rather than a dead end
- Processing restricted to directories you explicitly allow
Requirements
FFmpeg installed and on your PATH — Homebrew, Chocolatey or apt all work — plus Python 3.9 or higher. Add the video-editor package with uv and point your client at it. No API key and nothing to sign up for; everything runs against local files.
Setup effort
Build from source — get the source, then follow the project's own run instructions
USE CASES
Cutting a clip out of a long recording
Give the start and end timestamps in plain language and let the command be written for you.
Converting for a platform that will not take your file
Name the target format and let it re-encode, with progress instead of a silent wait.
Getting the audio out of a video
Ask for the audio track as a separate file rather than looking up the extraction flags.
Stitching several clips together
Merge the files in order in one call, and read the error detail if the codecs do not match.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
uv on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
uv run video-editorMCP Clients
Claude Desktop
{
"mcpServers": {
"video-editor": {
"command": "uv",
"args": [
"run",
"video-editor"
]
}
}
}