Clipkit

Clipkit gives your AI a complete video toolbox built on the Clipkit Protocol — an open, documented JSON format for describing videos (scenes, text, shapes, images, audio, animations, captions, charts).

What your AI can do with it:

MCP connector

Server URL: https://www.clipkit.dev/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: Clipkit MCP — author Clipkit Protocol videos via tools, and read the canonical authoring docs as resources. BEFORE composing, call for the authoring guide ( topic:"protocol" for field semantics, topic:"brand" for brand-correct visuals). For exact field names + types call (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 . 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) — 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 / / . SEE YOUR WORK — you cannot otherwise see the video: call for a frame, and / for a structural read-back with render-time warnings. The loop is edit → → 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 to host it and get a stable url for an element's url. DELIVER: ALWAYS deliver by calling 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. 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: / / / return a project_id; pass it to EVERY subsequent tool call ( / / / / revisions / render_video / …). REVISIONS: one video = ONE project. When the user asks for changes, update the SAME project_id ( with project_id, or ) — never create a second project for an iteration; that strands the previous version and breaks the editor link you already shared. Only the local single-project stdio server may omit project_id.

Tools

Reads data6

Changes data5

Deletes or can't be undone4

Skills

None in the store listings or on the server

MCP connector

Server URL

https://www.clipkit.dev/mcp

None

Protocol

MCP 2025-11-25

Instructions

Clipkit MCP — author Clipkit Protocol videos via tools, and read the canonical authoring docs as resources. BEFORE composing, call for the authoring guide ( topic:"protocol" for field semantics, topic:"brand" for brand-correct visuals). For exact field names + types call (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 . 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) — 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 / / . SEE YOUR WORK — you cannot otherwise see the video: call for a frame, and / for a structural read-back with render-time warnings. The loop is edit → → 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 to host it and get a stable url for an element's url. DELIVER: ALWAYS deliver by calling 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. 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: / / / return a project_id; pass it to EVERY subsequent tool call ( / / / / revisions / render_video / …). REVISIONS: one video = ONE project. When the user asks for changes, update the SAME project_id ( with project_id, or ) — never create a second project for an iteration; that strands the previous version and breaks the editor link you already shared. Only the local single-project stdio server may omit project_id.