About Kodecz
Kodecz is an open-source engine and MCP server for rendering web pages into MP4 video on NVIDIA GPUs or CPUs. It gives video creators and agents tools to render, inspect frames, and run automated checks.
Key features
- 01Render video folders to MP4
- 02Preview selected frames as PNG images
- 03Check text placement and caption length
- 04Check safe areas, contrast, and zoom timing
Use cases
- 01Render a web-page video project to MP4
- 02Inspect frames during video iteration
- 03Find layout and readability issues automatically
MCP support
The MCP server exposes Kodecz's render, preview, and check commands as tools to MCP clients. It runs an installed `kodecz` command on the host machine.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y kodecz-mcpKODECZ_BINPath to the kodecz command (default: kodecz on the PATH)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
3Saved tool list · updated 2d ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| id | string | Yes | The id in the page's <script type="application/json" id="kodecz"> block |
| cpu | boolean | No | Render on the CPU even when there is a GPU |
| from | integer | No | First frame to render |
| hevc | boolean | No | HEVC instead of H.264 (GPU only) |
| alpha | boolean | No | Transparent layer as raw HEVC with alpha (GPU only, no audio) |
| folder | string | Yes | Video folder (the one with index.html), absolute or relative to the working directory |
| frames | integer | No | How many frames to render from `from` |
| output | string | Yes | Output file (.mp4; .hevc with alpha) |
Details
From the project READMEkodecz-mcp
MCP server for Kodecz, the open-source engine that renders a web page into an MP4 on an NVIDIA GPU or on any CPU. It gives any MCP client the three commands of the Kodecz loop:
| Tool | What it does |
|---|---|
render | renders a video folder to MP4 (cpu, hevc, alpha, from, frames); returns the render's JSON line |
preview | draws the given frames as lossless PNGs and returns them as images, so the agent can look |
check | runs the automatic checks on every frame (text over a face, one-line captions, safe area, contrast, zoom timing); returns the JSON result and pictures of the problems |
The server has no dependencies. It runs the kodecz command already installed on the machine (set KODECZ_BIN to
another path), with an argument list and never through a shell, so Kodecz itself must be installed first
(quick start).
Use
Claude Code: the Kodecz plugin starts it for you (/plugin install kodecz --marketplace konecz/kodecz).
Any other client (Claude Desktop, Cursor, Codex, VS Code...):
{ "mcpServers": { "kodecz": { "command": "npx", "args": ["-y", "kodecz-mcp"] } } }
From a clone, without npm: "command": "node", "args": ["/path/to/kodecz/mcp/kodecz-mcp.mjs"].
Paths in tool calls are absolute or relative to the server's working directory. Tests: node --test mcp/kodecz-mcp.test.mjs.
Apache-2.0. Created by Konecz.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.