clipkit.dev

Clipkit MCP — author Clipkit Protocol videos via tools, and read the canonical authoring docs as resources. BEFORE composing, call read_docs for the authoring guide (read_docs topic:"protocol" for field semantics, topic:"brand" for brand-correct visuals). For exact field names + types call get_schema (optionally with an element_type). These are TOOLS, not resources, so you can read them directly. TWO WAYS TO BUILD — pick by the brief, do NOT default to one: (A) AUTHOR IT YOURSELF — write a full source JSON and call set_project. This is the full creative canvas: every element type (text, image, video, shape, audio, group, caption, particles) plus effects, 3D camera, lighting, gradients, keyframe animation, and expressions. Use this for anything specific, original, or not a stock promo — most briefs. (B) create_promo — a FAST path that assembles a conventional promo/intro/product/data video from prebuilt scenes (it handles camera/glass/lighting/motion/layout). Good when a template fits; it is ONE option, not the default. Mix scene types and fit the structure to the content — do NOT reflexively make a glass-orb hero + CTA. TWEAK an existing project with add_element / edit_element / delete_element. SEE YOUR WORK — you cannot otherwise see the video: call preview_still for a frame, and validate_project / describe_project for a structural read-back with render-time warnings. The loop is edit → preview_still → fix. CAPTIONS: transcribe_to_captions turns a media url (or local file) into a timed caption. MEDIA: to use an image/video/audio that is not already a stable public URL (or to make a link durable so it cannot rot), call ingest_asset to host it and get a stable url for an element's `url`. DELIVER: ALWAYS deliver by calling open_in_editor and giving the user that free link — it opens the project in the editor where they preview and render the video themselves in the browser. This is the default and almost always what you want. load_project re-imports a shared project by id/URL. Do NOT call render_video unless the user EXPLICITLY asks you to render/export a finished MP4 file for them; it is the paid cloud path (consumes credits, needs CLIPKIT_API_KEY) and is not offered on the hosted connector. PROJECT IDS: create_project / set_project / create_promo / load_project return a project_id; pass it to subsequent tools (get_project / edit_element / preview_still / validate_project / render_video / …). When working on a single local project you may omit it.