# LeClap

> Deterministic video from one JSON template — same input, same frames, rendered locally.

- **Category:** Editing & Post
- **Vendor:** Community (heristop) (community)
- **Pricing:** free
- **Verified:** 2026-09-04

## What it does

LeClap exposes its ffmpeg-video-composer engine over MCP: the agent asks for the template JSON Schema, authors a descriptor of sections, filters, music and text overlays, validates it for free, then renders it to an MP4 on the machine. Nothing is sampled and nothing is uploaded, so the same template produces the same frames on every run — the opposite trade to a generative model, and the right one for titles, lower thirds, and any card you will need to re-render at 3am with one word changed. An opt-in bridge renders compositions from your own Remotion project into a clip the deterministic engine then composites.

## Connect

- Claude Code: `claude mcp add leclap -e LECLAP_MCP_MEDIA_DIR=/abs/path/to/media -e LECLAP_MCP_OUTPUT_DIR=/abs/path/to/renders -- npx -y @leclap/mcp`
- Local: `npx -y @leclap/mcp`

**Auth:** none

## Capabilities

[template-video](https://mcp.film/capabilities/template-video.md) · [video-assembly](https://mcp.film/capabilities/video-assembly.md) · `deterministic-render` · [ffmpeg](https://mcp.film/capabilities/ffmpeg.md) · [local-post](https://mcp.film/capabilities/local-post.md) · [motion-graphics](https://mcp.film/capabilities/motion-graphics.md)

## Sample tools

`get_template_schema` · `validate_template` · `compose_video` · `probe_media` · `render_remotion_clip` · `ping`

## Field notes

First-party to the LeClap project — the MCP package lives in its monorepo — but that project is one maintainer's open-source work, not a company, so it is listed as community. MIT, 24 stars on the monorepo, npm @leclap/mcp 0.3.4 (24 Aug 2026), listed in the official MCP registry as dev.leclap/video. Node >=24.11.0 — an unusually aggressive floor that will bounce most CI images and any Node 22 LTS setup. FFmpeg is not bundled for the npx path: the engine looks for a system binary first and falls back to an optional `ffmpeg-static` that `npx -y @leclap/mcp` will not install for you, so put ffmpeg on PATH. Set LECLAP_MCP_MEDIA_DIR deliberately — local inputs must resolve inside it via a symlink-safe containment check, and pointing it at your home directory hands every tool call the run of it. `render_remotion_clip` runs your project's own JavaScript under headless Chromium and is therefore off unless you pass --allow-remotion; it also needs @remotion/renderer and @remotion/bundler installed yourself, and Remotion's own licence applies. Determinism is per platform, not across them — Node and browser encode with libx264, Android with libopenh264, iOS with h264_videotoolbox, and the on-device build silently drops boxblur and rewrites eq to lutyuv. There is no template catalogue; the server authors descriptors from the schema. Renders are 10-minute-capped by default. The MCP package is under a month old — read it as promising, not proven.

## Verification

- Status: Freshly checked (checked today)
- Added: 2026-09-04
- Last verified: 2026-09-04
- Machine JSON: https://mcp.film/api/mcps/leclap.json

## Links

- Site: https://leclap.dev/?utm_source=mcp.film&utm_medium=referral&utm_campaign=directory&utm_content=leclap%3Asite
- Docs: https://github.com/heristop/leclap/tree/main/packages/leclap-mcp?utm_source=mcp.film&utm_medium=referral&utm_campaign=directory&utm_content=leclap%3Adocs#readme
- Repo: https://github.com/heristop/leclap

---

Structured data: https://mcp.film/api/mcps/leclap.json · Directory: https://mcp.film