mcpField
C
Clipkit

Clipkit

VerifiedFeaturedLocal
clipkit.devMedia & Design19Updated 11w ago

About Clipkit

Clipkit is video infrastructure for AI agents that renders MP4 files from a JSON timeline written in the open ClipKit Protocol. It targets agent builders and developers who want structured, deterministic video generation. Documents can be validated before rendering, and output can be produced locally or on a hosted GPU service.

Key features

  1. 01Motion-graphics video described as a JSON document
  2. 02Protocol validation and plain-language summaries before rendering
  3. 03Local MP4 rendering through headless Chrome
  4. 04Hosted cloud rendering with ProRes, AV1 and transparent output
  5. 05Embeddable editor and speech-to-text caption packages

Use cases

  1. 01Letting an agent build motion-graphics videos from structured data
  2. 02Rendering customer-facing videos from code in batch
  3. 03Generating captions or analyzing beats for video projects

MCP support

The project includes @clipkit/mcp-server, started with npx -y @clipkit/cli mcp over stdio, so agents can author, validate, preview and render ClipKit videos.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"clipkit": {
"command": "npx",
"args": [
"-y",
"@clipkit/cli"
]
}
}
}
Run commandnpx -y @clipkit/cli

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@clipkit/cli

Tools

16

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
topicenumNoWhich doc. Default "agents".agents | protocol | brand | card | pattern-data-viz | pattern-cinematic-ui | pattern-ui-screencast | pattern-lighting | pattern-promo-teaser

Details

From the project README

ClipKit

The video infra for agents. ClipKit turns a JSON timeline — the open ClipKit Protocol — into rendered video on the GPU. Describe a video as structured data; get an MP4. Built for AI agents and the developers shipping them.

clipkit.dev · Docs · Protocol · Agent quickstarts

https://github.com/user-attachments/assets/ff4b7e9b-2e0a-40f4-a6a1-042e981fc65f

↑ Made with ClipKit. Every frame of this promo was rendered from a ClipKit Protocol document — no editor, no timeline UI, just structured data. ▶ Play if it doesn't load inline.

Quick start

npm install -g @clipkit/cli

clipkit new my-video.json                 # scaffold a Source
clipkit render my-video.json -o out.mp4   # render locally (headless Chrome)

…or from code:

import { render } from '@clipkit/renderer';
import { writeFile } from 'node:fs/promises';

const { buffer } = await render({ source });   // source = a ClipKit Protocol document
await writeFile('out.mp4', buffer);

Local rendering uses your installed Google Chrome (for WebCodecs). For GPU-accelerated and pro-format (ProRes / AV1 / transparent) output, render on the hosted service with clipkit render --cloud.

What's here

A monorepo; each package publishes to npm under the @clipkit scope.

PackageWhat it is
@clipkit/protocolthe ClipKit Protocol — schema, types, validation
@clipkit/runtimethe engine — WebGPU/WebGL2 compositor + WebCodecs encoder
@clipkit/rendererrender a Source to MP4 locally (headless Chrome)
@clipkit/editora configurable, embeddable editor over the schema
@clipkit/editor-corethe editor's UI-free data layer
@clipkit/playbackbrowser playback engine
@clipkit/patternscomposable motion-graphics units
@clipkit/sfxprocedural sound-effects synthesis
@clipkit/music-analysisbeat / tempo analysis for authoring
@clipkit/speech-to-texttranscription → captions
@clipkit/lintprotocol-aware validation + plain-language summaries
@clipkit/mcp-serveran MCP server so agents can author + render video
@clipkit/clithe local-first CLI

For AI agents

ClipKit ships an MCP server — point your agent at it and it can build, validate, preview, and render ClipKit videos:

npx -y @clipkit/cli mcp        # stdio MCP server

See the agent quickstarts for Claude, Cursor, and more.

License

Apache-2.0 — except @clipkit/runtime, which is under the Business Source License 1.1 and converts to Apache-2.0 four years after each release. In plain terms: use it, embed it, build your own product on it, and render for your own customers — all free. The one thing you can't do is offer a competing hosted ClipKit-rendering service. See LICENSING.md and TRADEMARK.md.

Comments

Markdown supported

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.