Parallel video rendering tools: detect GPU encoders, render, color grade, merge audio, concat.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Render video from code, in parallel. You write one function that paints a frame; ffmpeg-render-pro splits the frame range across worker threads, encodes one MP4 segment per worker, joins the segments with stream copy (no re-encode), and shows a live dashboard in your browser while it runs. It also detects GPU encoders, grades color, merges audio, and ships as a CLI, a Node library, an MCP server for AI agents, and a Claude Code skill.
Built by Beeswax Pat. Free and open source.
Three commands. You need Node.js 18 or newer and ffmpeg on your PATH.
Open my-worker.js. The only function you need to change is renderFrame(frameNum, buffer): fill the buffer with your pixels (B, G, R, A, one row after another) and everything else is already done. Derive any randomness from the seed it receives and parallel output stays identical to a sequential render.
Install it globally if you would rather not type npx:
The variables are read at call time, so a long-running process such as the MCP server picks up changes without a restart.
Render and benchmark flags: --width=1920 --height=1080 (must be even), --fps=60, --duration=60 (fractions allowed), --output=out.mp4, --workers=N, --max-workers=8, --seed=42, --title="...", --crf=20 (0-51, lower is higher quality), --encoder-preset=fast (any x264 preset). Dashboard flags: --no-dashboard, --no-open, --port=8080, --linger-ms=30000 (0 exits as soon as the render finishes). Run ffmpeg-render-pro with no arguments for the full list.
An unknown flag warns and continues. A value that does not parse, such as --fps=abc, exits 1 instead of rendering at the default.
Installed binaries: ffmpeg-render-pro (this CLI) and ffmpeg-render-pro-mcp (the MCP server). The older ffmpeg-render-mcp name still works so existing MCP configs never break.
renderParallel checks ffmpeg, validates the resolution, and picks a worker count from your CPU cores and RAM (never more workers than frames).127.0.0.1 and opens your browser.workerData, pipes raw BGRA frames into its own ffmpeg process, and writes one MP4 segment.-c copy, which takes seconds regardless of length.A worker is a Node script that runs in a worker_threads thread. init gives you one where only renderFrame needs editing; examples/basic-worker.js in the installed package is a larger reference with a particle system and seeded RNG.
Fields the renderer injects through workerData:
| Field | Meaning |
|---|---|
width, height, fps | Frame size and rate |
seed | Derive every random value from this |
startFrame, endFrame | Render exactly [startFrame, endFrame) |
segmentPath | Write this worker's MP4 here |
workerId | Include it in every message you post |
totalFrames, duration | Whole-video totals, for global effects such as a progress bar |
anything in renderParallel({ workerData }) | Your own extra keys (the bundled workers honor codecArgs) |
Messages the worker posts with parentPort.postMessage:
| Message | When | Fields |
|---|---|---|
{ type: 'progress' } | periodically | workerId, pct, fps, frame, eta |
{ type: 'fast-forward-start' } | optional, before replaying state to reach startFrame | workerId, frames |
{ type: 'done' } | once, after the segment is fully written | workerId |
{ type: 'error' } | on failure, never followed by done | workerId, error |
Every worker must encode with the same codec, resolution, framerate, and pixel format, because the segments are stream-copied together.
Abort rejects with an error whose name is 'AbortError'. In library use set dashboardLingerMs: 0 so the call returns without holding the process open. Set FFMPEG_RENDER_PRO_DEBUG=1 for full stack traces from the CLI.
colorGrade accepts any encoder name in codec; encoders that need their own filter (VA-API) get it merged into the grade chain automatically.
For multi-hour renders, snapshot your simulation state every N frames once, so each worker replays only the frames since the nearest snapshot instead of starting from frame 0.
systems is an object of named modules with getState(), setState(), and update(dt). A checkpoint labeled frame F holds exactly F updates. _frame and _timestamp are reserved keys.
Seven tools over stdio, usable from Claude Code, Claude Desktop, or any MCP client.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/ffmpeg-render-pro)<a href="https://allmcps.com/mcp/ffmpeg-render-pro"><img src="https://allmcps.com/api/badge/ffmpeg-render-pro?style=directory" alt="Ffmpeg Render Pro on AllMCPs" /></a>