probe_video
Probe a local video file for duration, dimensions, codecs and format
file_pathrequired
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 7, 2026
Probe, trim, transcode and extract frames or audio from local video files with ffmpeg.
Local stdio MCP server that lets an assistant inspect and edit local video files with ffmpeg: probe, thumbnail, frames, audio, trim, transcode, resize.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
Local video file tools as a CLI and a stdio MCP server in one bin. Probe a video for duration, dimensions and codecs; extract a thumbnail, frames or the audio track; trim, transcode and resize.
All work is built as ffmpeg/ffprobe argument arrays (execFile, never a shell string) behind an injectable executor, and probe results are parsed from ffprobe's JSON output — fields a file does not carry come back as null, never invented. This package bundles no ffmpeg: host runs use the host's binaries, and when they are absent the spawn error (ENOENT) is the tool error.
Exit codes: 0 success, 1 ffmpeg error, 2 usage error.
MCP client config:
MIT license.
Source: README.md at commit 5ea4c54
Probe a local video file for duration, dimensions, codecs and format
file_pathrequiredExtract a single frame of a video as a thumbnail image file
file_pathrequiredoutput_filerequiredtimestamp_secondsExtract frames of a video as image files in an output directory at a given rate
fpsfile_pathrequiredoutput_dirrequiredExtract the audio track of a video into an audio file
file_pathrequiredoutput_filerequiredTrim a video to a segment starting at an offset, optionally with a duration
file_pathrequiredoutput_filerequiredstart_secondsrequiredduration_secondsTranscode a video to another container format
formatrequiredfile_pathrequiredoutput_filerequiredResize a video to the given width and height
widthrequiredheightrequiredfile_pathrequiredoutput_filerequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npx -y @reneturcios/videokit mcpvideokit mcpvideokit probe <file>videokit thumbnail <file> <output> [timestamp-seconds]videokit audio <file> <output>videokit trim <file> <output> <start-seconds> [duration-seconds]videokit resize <file> <output> <width> <height>videokit --version{ "mcpServers": { "videokit": { "command": "npx", "args": ["-y", "@reneturcios/videokit", "mcp"] } }}docker run -i ghcr.io/cloudcorprecords/videokit # MCP server (ffmpeg unavailable in-image)docker run --rm ghcr.io/cloudcorprecords/videokit --versionnpm installnpm run buildnpm test