Clipkit
OfficialRelated Servers
Alternatives to Clipkit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to edit video locally through FFmpeg: probing media, validating and previewing JSON edit projects, rendering short-form clips with captions, reframing, transitions and ducked music. Also analyses existing videos and applies or saves reusable format templates, without cloud services or API keys.Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI coding agents to programmatically assemble vertical videos and manage local CapCut Desktop drafts, including AI background removal, audio mastering to -14 LUFS or Demucs vocal isolation, music auto-ducking, punch zooms, karaoke captions, PiP proof overlays, hook badges, safe-zone linting, proxy previews, and EN→ES cloning/dubbing. It outputs real CapCut draft JSON ready for review and export.172MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to create and edit animated video projects through 93 tools covering scenes, elements, audio, subtitles, themes, previews, and rendering. It shares live project state with a browser-based editor so agent and user edits stay synchronized.785 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to automate video editing tasks such as creating, inspecting, and saving projects, adding, splitting, and deleting clips, applying kinetic motion behaviors, and validating render parameters. Supports JSON-RPC 2.0 over stdio and HTTP.MIT
- FlicenseNot gradedqualityAmaintenanceEnables users to turn raw video clips into finished, beat-synced montage cuts through natural-language chat, automating shot selection, pacing, music matching, subtitles, transitions, picture-in-picture, and rendering. It returns reviewable timeline digests and contact sheets before rendering so edits can be approved in chat.-

DT.ly MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to author and refine JSON-based motion-graphics compositions by editing layers, keyframes, easing curves, text animators, masks, effects, and other animation properties, then previewing rendered frames or video output.1,137 npmMIT
TDQS
Scored across 16 tools
Each tool targets a distinct action and object: project CRUD, element tweaks, validation, preview, transcription, promo assembly, editor sharing, and rendering. The descriptions explicitly contrast overlapping tools (set_project vs create_project, get_project vs describe_project), so an agent should never confuse them.
All 16 tools follow a strict verb_noun pattern with snake_case (create_project, edit_element, render_video). There are no mixed conventions or vague verb-only names, and the verb consistently reflects the operation (get, set, add, edit, delete, validate, preview, render, open, load, transcribe, create).
At 16 tools, this is just one over the typical 3-15 sweet spot, but the server's scope is a full video authoring and rendering pipeline, and every tool serves a distinct stage of that pipeline. It feels appropriately scoped rather than bloated.
The tool surface covers the full lifecycle: project creation and replacement, element CRUD, validation with render warnings, still preview, caption transcription, template-based assembly, editor round-tripping, and paid rendering. There are no obvious dead ends—any operation an agent needs is present.