{
  "markdown": "# ClipKit\n\n**The video infra for agents.** ClipKit turns a JSON timeline — the open\n**ClipKit Protocol** — into rendered video on the GPU. Describe a video as\nstructured data; get an MP4. Built for AI agents and the developers shipping them.\n\n[clipkit.dev](https://clipkit.dev) · [Docs](https://clipkit.dev/docs) · [Protocol](https://clipkit.dev/docs/protocol) · [Agent quickstarts](https://clipkit.dev/docs/mcp)\n\nhttps://github.com/user-attachments/assets/ff4b7e9b-2e0a-40f4-a6a1-042e981fc65f\n\n<p align=\"center\"><sub><b>↑ Made with ClipKit.</b> Every frame of this promo was rendered from a ClipKit Protocol document — no editor, no timeline UI, just structured data. <a href=\"https://api.clipkit.dev/storage/v1/object/public/remote-assets/clipkit-promo.mp4\">▶&nbsp;Play</a> if it doesn't load inline.</sub></p>\n\n## Quick start\n\n```bash\nnpm install -g @clipkit/cli\n\nclipkit new my-video.json                 # scaffold a Source\nclipkit render my-video.json -o out.mp4   # render locally (headless Chrome)\n```\n\n…or from code:\n\n```ts\nimport { render } from '@clipkit/renderer';\nimport { writeFile } from 'node:fs/promises';\n\nconst { buffer } = await render({ source });   // source = a ClipKit Protocol document\nawait writeFile('out.mp4', buffer);\n```\n\nLocal rendering uses your installed Google Chrome (for WebCodecs). For GPU-accelerated\nand pro-format (ProRes / AV1 / transparent) output, render on the hosted service with\n`clipkit render --cloud`.\n\n## What's here\n\nA monorepo; each package publishes to npm under the `@clipkit` scope.\n\n| Package | What it is |\n|---|---|\n| [`@clipkit/protocol`](packages/protocol) | the ClipKit Protocol — schema, types, validation |\n| [`@clipkit/runtime`](packages/runtime) | the engine — WebGPU/WebGL2 compositor + WebCodecs encoder |\n| [`@clipkit/renderer`](packages/renderer) | render a Source to MP4 locally (headless Chrome) |\n| [`@clipkit/editor`](packages/editor) | a configurable, embeddable editor over the schema |\n| [`@clipkit/editor-core`](packages/editor-core) | the editor's UI-free data layer |\n| [`@clipkit/playback`](packages/playback) | browser playback engine |\n| [`@clipkit/patterns`](packages/patterns) | composable motion-graphics units |\n| [`@clipkit/sfx`](packages/sfx) | procedural sound-effects synthesis |\n| [`@clipkit/music-analysis`](packages/music-analysis) | beat / tempo analysis for authoring |\n| [`@clipkit/speech-to-text`](packages/speech-to-text) | transcription → captions |\n| [`@clipkit/lint`](packages/lint) | protocol-aware validation + plain-language summaries |\n| [`@clipkit/mcp-server`](packages/mcp-server) | an MCP server so agents can author + render video |\n| [`@clipkit/cli`](packages/cli) | the local-first CLI |\n\n## For AI agents\n\nClipKit ships an MCP server — point your agent at it and it can build, validate,\npreview, and render ClipKit videos:\n\n```bash\nnpx -y @clipkit/cli mcp        # stdio MCP server\n```\n\nSee the [agent quickstarts](https://clipkit.dev/docs/mcp) for Claude, Cursor, and more.\n\n## License\n\nApache-2.0 — **except [`@clipkit/runtime`](packages/runtime)**, which is under the\n[Business Source License 1.1](LICENSING.md) and converts to Apache-2.0 four years after\neach release. In plain terms: use it, embed it, build your own product on it, and render\nfor your own customers — all free. The one thing you can't do is offer a competing\n*hosted* ClipKit-rendering service. See [LICENSING.md](LICENSING.md) and\n[TRADEMARK.md](TRADEMARK.md).\n",
  "bytes": 3446,
  "sha": "8b93a2299153b360eb8e7506654609933152939348173fb127fbdd3fff34a3ab",
  "repo_slug": "clipkit-video/clipkit",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_dev_clipkit_clipkit_e2d76907/readme"
}