# clipkit MCP server

MCP server for Clipkit — gives AI agents a video toolbox via the Clipkit schema.

## Links
- Registry page: https://www.getdrio.com/mcp/dev-clipkit-clipkit
- Repository: https://github.com/clipkit-video/clipkit

## Install
- Endpoint: https://www.clipkit.dev/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://www.clipkit.dev/mcp

## Tools
- read_docs (Read the Clipkit authoring docs) - Return a canonical Clipkit doc as text. topic "card" = the ~8KB compact authoring card — the recommended context for authoring; "pattern-data-viz" / "pattern-cinematic-ui" / "pattern-ui-screencast" = ~4-5KB archetype pattern cards (proven idioms: count-ups and bar rows; product hero shots with camera rigs; faked app UI with typing/cursor/clicks) — load ONE alongside the card when the brief matches its archetype; "agents" = the full authoring guide (fetch only when the card doesn't cover a need); "protocol" = the formal field spec; "brand" = brand reference. (Same docs offered as MCP resources, exposed as a tool so you can read them directly — resources are not always model-readable.) Endpoint: https://www.clipkit.dev/mcp
- get_schema (Get the Clipkit JSON Schema (exact fields)) - Return the authoritative JSON Schema for a Clipkit Source — exact field names, types, and enums, generated from the protocol. Call with no argument for the full Source schema, or with element_type (e.g. "text", "shape", "particles") for just that element's fields (much smaller). Use this when authoring with set_project / add_element so you never guess a field. Endpoint: https://www.clipkit.dev/mcp
- create_project (Create a new Clipkit project) - Create a new, blank Clipkit project with the given dimensions and duration, and return its project_id. Defaults: 1920×1080, 10 seconds, 30 fps, output_format "mp4". Call this first when starting a new video. Pass an existing project_id to reset that project to blank; omit it to start a fresh project (note the returned id for subsequent tools). Endpoint: https://www.clipkit.dev/mcp
- get_project (Get the current Clipkit project JSON) - Return the full current Clipkit source as JSON. Use this to inspect the project, pass it to a render pipeline, or compose follow-up edits. Endpoint: https://www.clipkit.dev/mcp
- describe_project (Describe the current project in plain language) - Return a compact, human-readable summary of the current project — dimensions, fps, duration, an element breakdown by type, a per-track timeline (paint order low→high), and render-time warnings. Much cheaper to read than get_project's full JSON; use it to orient yourself or sanity-check structure without dumping the whole source. Endpoint: https://www.clipkit.dev/mcp
- set_project (Replace the entire Clipkit project) - Replace the entire project with the given source JSON, returning its project_id. This is the PRIMARY way to build: use it to create a composition or to add/change many elements at once. (To tweak a single element in an existing project, use edit_element / add_element / delete_element instead.) Pass an existing project_id to replace that project; omit it to create a new one (note the returned id). The input is validated against the @clipkit/protocol before being accepted; invalid inputs return an error. Shape: { width, height, duration, frame_rate, output_format, background_color?, fonts?, camera?, lights?, elements:[…] }; every element has a `type` plus base fields (id, x, y, width, height, time, duration, track, opacity, rotation, animations, keyframe_animations) and type-specific fields. For exact field names + types call get_schema (optionally with an element_type) — the runtime ignores unrecognized keys, and this tool flags any it does not recognize. Endpoint: https://www.clipkit.dev/mcp
- add_element (Add an element to the current project) - Append a single element to an existing project — a TWEAK, e.g. dropping in one more caption or shape. By default it is added at the top level; pass parent_id to add it INTO a group (nested). The element is any valid schema element: video, image, text, shape, audio, group, caption, or particles. To create a composition or add several elements at once, build the JSON and use set_project instead. The new element is validated as part of the project as a whole before being added. Call get_schema(element_type) for the exact per-type fields; unrecognized keys are flagged. Endpoint: https://www.clipkit.dev/mcp
- edit_element (Tweak one existing element (merge changed fields)) - Change fields on the element with the given id by merging in a partial element — only the keys you include change. The id may be any element ANYWHERE in the tree, including one nested inside a group (or its mask). Pass a whole nested value (e.g. a new `keyframe_animations` array) to replace that key; set a key to null to remove it. This is for TWEAKING an existing composition. To create a composition or change many elements at once, edit the JSON and call set_project instead. The result is re-validated before being accepted. Endpoint: https://www.clipkit.dev/mcp
- delete_element (Delete one element by id) - Delete the element with the given id, anywhere in the tree (including one nested inside a group or its mask) — a tweak to an existing composition. (The project must keep at least one top-level element.) Endpoint: https://www.clipkit.dev/mcp
- validate_project (Validate the current project (schema + render-time warnings)) - Run the @clipkit/protocol validator against the current project AND surface render-time warnings even when the JSON is valid — things that pass the schema but the runtime will silently drop or clip: emoji / non-ASCII text (the runtime font atlas is ASCII-only), elements that run past the composition end, a missing top-level duration. Run it before you share or render the project. For a fuller timeline read-back, use describe_project. Endpoint: https://www.clipkit.dev/mcp
- preview_still (Render one frame of the current project so you can SEE it) - Render a single frame of the current project to a PNG and return it as an image you can look at. This is how you check your work — in chat there is no other way to see what a composition actually looks like. Use it liberally: after composing, after edits, and at different times to inspect motion. Stills are FREE (credits are only spent by render_video). Pass `time` (seconds) to choose the frame; defaults to 0. Endpoint: https://www.clipkit.dev/mcp
- create_promo (Compose a designed promo from prebuilt scenes (one fast option)) - Assemble a designed-looking promo/intro/product/data video from the Clipkit pattern library: give an ordered list of SCENES and the words, and it bakes in the camera, glass, lighting, motion blur, timing, and layout, then returns an editor link. This is a FAST option when a conventional promo structure fits — it is NOT the only way to make a video and NOT a default; for anything specific or original, author the JSON yourself and call set_project (the full creative range). When you do use this, MIX scene types to fit the brief and vary the structure — a video can be a single kinetic headline, three title cards, a showcase montage, or a data explainer; you do NOT need a hero or a cta. Scene types: hero (glass-orb logo reveal: wordmark, tagline?), kinetic (letter-fly headline: text, subtitle?), showcase (a screenshot tilted in 3D: screenshot URL), title (full-frame title card: headline, kicker?, subtitle?), cta (closing card with a glass button: wordmark, tagline?, cta), stats (hero numbers: stats[{label,current,previous?}], title?), bars (bar chart: bars[{label,value,previous?}], title?), ranking (top-N list: items[{label,value}], title?), pie (pie cards: cards[{label,value,total,previous?}], title?). The data scenes (stats/bars/ranking/pie) look best with theme "mux". Endpoint: https://www.clipkit.dev/mcp
- open_in_editor (Create a shareable link that opens the current project in the editor) - Validate the current project and create a link that opens it in the Clipkit web editor, where the user can preview and refine it. This shares the PROJECT (nothing is rendered — that's render_video). Use after composing or editing. Returns a URL. Endpoint: https://www.clipkit.dev/mcp
- ingest_asset (Host a remote image/video/audio so a project can use it) - Fetch a remote media URL (image/video/audio) and HOST it on Clipkit, returning a stable asset_url to put in an element's `url`. Use this so the project's media survives — the original link may rot, be private, or block hotlinking. Anonymous projects allow up to 5 hosted assets / 100 MB total / 50 MB per file; when the limit is hit, tell the user to open the project (open_in_editor) and sign in to add more. Requires project_id. Endpoint: https://www.clipkit.dev/mcp
- load_project (Load a shared project back into the session) - Import a previously shared project as the current project, by its share id or its editor URL (e.g. https://clipkit.dev/editor?id=…), returning its project_id. Use this to continue working on a project the user opened in the editor or shared earlier — the round-trip for open_in_editor. Pass an existing project_id to load into that project; omit it to load into a new one. Endpoint: https://www.clipkit.dev/mcp

## Resources
- clipkit://docs/agents.md - Clipkit — Authoring guide (AGENTS.md) AI authoring reference for Clipkit videos. Schema cheat sheet, pattern catalog (HeaderBar / StatBlock / BarChartRow / RankedList / PieCard), recipe gallery pointing at the working example videos, and authoring guidance (pacing, count-ups, staggers). Read this before composing a video. MIME type: text/markdown
- clipkit://docs/protocol.md - Clipkit Protocol v1.0 (PROTOCOL.md) Normative specification for the Clipkit Protocol (CKP/1.0). RFC 2119 voice — defines Source structure, every element type, the animation model, easing functions, conformance levels (validate / render / export), versioning, and the extension namespace. Source of truth for implementers. MIME type: text/markdown
- clipkit://docs/brand.md - Clipkit Brand reference (BRAND.md) Brand identity: dark surface system (#0A0A0A), two accents only (red #EF4444 + yellow #FFB800), Geist + Geist Mono typography, the three-bar logo construction, voice & tone (direct / concrete / honest / no hype). Use when producing Clipkit-branded assets. MIME type: text/markdown
- clipkit://schema/source.json - Clipkit Source — JSON Schema Machine-readable JSON Schema for a Clipkit Source, generated from the protocol Zod source of truth. The EXACT shape for set_project / add_element — every field, every element type, with types and enums. Read it to author correct JSON instead of guessing field names. (Agents that cannot read resources: use the get_schema tool instead.) MIME type: application/json

## Prompts
Not captured

## Metadata
- Owner: dev.clipkit
- Version: 1.0.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jul 16, 2026
- Source: https://registry.modelcontextprotocol.io