# dev.clipkit/clipkit (remote · www.clipkit.dev)

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

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `www.clipkit.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/dev-clipkit-clipkit/www.md), [page](https://verifymcp.io/servers/dev-clipkit-clipkit/www)

## Channel facts

- Endpoint: `https://www.clipkit.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (set_project).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3689 tokens (~194/item across 19 items; 15 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (73% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http dev-clipkit-clipkit https://www.clipkit.dev/mcp
```

### Codex

```toml
[mcp_servers.dev-clipkit-clipkit]
url = "https://www.clipkit.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-clipkit-clipkit": {
      "type": "remote",
      "url": "https://www.clipkit.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-clipkit-clipkit --url https://www.clipkit.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-clipkit-clipkit:
    url: "https://www.clipkit.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "dev-clipkit-clipkit": {
      "type": "http",
      "url": "https://www.clipkit.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 66, 0)

- [security] Tool “read_docs” rewrote its description, which is the text the model reads

### 2026-07-27 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (15)

### `read_docs` (~190 tokens)

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.)

Input parameters:

- `topic` (string): Which doc. Default "agents".

### `get_schema` (~119 tokens)

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.

Input parameters:

- `element_type` (string): Limit to one element type's fields (e.g. "text"). Omit for the full Source schema (large).

### `create_project` (~280 tokens)

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).

Input parameters:

- `background_color` (string): Hex color, e.g. "#000000".
- `duration` (number): Composition duration in seconds. Default 10.
- `frame_rate` (number): Frame rate. Default 30.
- `height` (integer): Composition height in pixels. Default 1080.
- `output_dither`: Anti-banding output dither — DEFAULT ON, leave unset. Pass false for byte-exact undithered output, or { amplitude, pattern } to tune. Stops gradients / soft shadows / blur from showing 8-bit banding;…
- `output_format` (string): Output container/codec. Default "mp4".
- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.
- `width` (integer): Composition width in pixels. Default 1920.

Output parameters:

- `duration` (number)
- `frame_rate` (number)
- `height` (number)
- `output_format` (string)
- `project_id` (string): Id of the created project — pass to subsequent tools.
- `width` (number)

### `get_project` (~78 tokens)

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.

Input parameters:

- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.

### `describe_project` (~114 tokens)

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.

Input parameters:

- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.

### `set_project` (~272 tokens)

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.

Input parameters:

- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.
- `source` (object, required): A full Clipkit source object.

Output parameters:

- `duration` (number)
- `element_count` (number)
- `height` (number)
- `project_id` (string)
- `width` (number)

### `add_element` (~222 tokens)

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.

Input parameters:

- `element` (object, required): A Clipkit element object. Must include `type`.
- `parent_id` (string): Optional id of a group to add this element INTO (nested). Omit to add at the top level.
- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.

Output parameters:

- `added_element_id` (string)
- `element_type` (string)
- `parent_id` (string)
- `top_level_element_count` (number)

### `edit_element` (~212 tokens)

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.

Input parameters:

- `id` (string, required): The id of the element to edit.
- `patch` (object, required): Partial element: the fields to change. Omitted keys are left as-is; a key set to null is removed.
- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.

Output parameters:

- `changed_keys` (array)
- `element_id` (string)

### `delete_element` (~105 tokens)

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.)

Input parameters:

- `id` (string, required): The id of the element to delete.
- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.

Output parameters:

- `deleted_element_id` (string)
- `top_level_element_count` (number)

### `validate_project` (~136 tokens)

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.

Input parameters:

- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.

Output parameters:

- `duration` (number)
- `element_count` (number)
- `error_count` (number)
- `errors` (array)
- `height` (number)
- `unknown_keys` (array)
- `valid` (boolean)
- `warnings` (array)
- `width` (number)

### `preview_still` (~164 tokens)

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.

Input parameters:

- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.
- `time` (number): Composition time in seconds to capture. Default 0 (first frame).

Output parameters:

- `height` (number)
- `mime_type` (string)
- `time` (number)
- `width` (number)

### `create_promo` (~513 tokens)

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".

Input parameters:

- `height` (integer): Default 1080.
- `motion_blur` (integer): Supersampled motion-blur samples (≥2 enables it — nicer but slower to render). Default off.
- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.
- `scenes` (array, required): Ordered scenes; mix types to fit the brief — you do NOT need hero/cta. e.g. a single [{type:"kinetic",text:"…"}], a sequence [{type:"title",headline:"…"},{type:"showcase",screenshot:"…"},{type:"title…
- `theme` (string): Visual theme. Default "cinematic" (dark, serif, premium).
- `width` (integer): Default 1920.

Output parameters:

- `duration` (number)
- `editor_url` (string)
- `height` (number)
- `project_id` (string)
- `scene_count` (number)
- `width` (number)

### `open_in_editor` (~99 tokens)

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.

Input parameters:

- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.

Output parameters:

- `editor_url` (string)
- `project_id` (string)

### `ingest_asset` (~187 tokens)

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.

Input parameters:

- `filename` (string): Optional display name for the asset.
- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.
- `url` (string, required): A public http(s) URL to an image, video, or audio file.

Output parameters:

- `asset_id` (string)
- `asset_url` (string)
- `filename` (string)

### `load_project` (~153 tokens)

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.

Input parameters:

- `id_or_url` (string, required): A share id, or a clipkit.dev/editor?id=… URL.
- `project_id` (string): Which project to act on — the id returned by create_project / set_project / create_promo / load_project. Omit when working on a single local project.

Output parameters:

- `duration` (number)
- `element_count` (number)
- `height` (number)
- `project_id` (string)
- `width` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-clipkit-clipkit/www#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 68
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 66

## Links

- Remote endpoint: https://www.clipkit.dev/mcp
- Repository: https://github.com/clipkit-video/clipkit
- Changelog RSS feed: https://verifymcp.io/servers/dev-clipkit-clipkit/www/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-clipkit-clipkit/www/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dev-clipkit-clipkit/www