Clipkit
OfficialRelated Servers
Alternatives to Clipkit
No user-submitted related servers found.
Related Servers
- 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

faktry MCPofficial
AlicenseNot gradedqualityAmaintenanceExposes over 70 generation and editing tools for images, video, audio, PDFs, and 3D assets to any MCP-compatible client, with async job polling, saved-media libraries, and credit tracking. Users can produce product shots, voiceovers, subtitles, and more without leaving their chat client.1MIT- AlicenseNot gradedqualityAmaintenanceProvides a headless video editing workflow using portable JSON projects and Kdenlive for review, enabling automated video rendering and project management.10Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to turn a meeting recording and transcript into captioned clips, trailers, longform best-ofs, and 1:1/9:16/16:9 social videos. Agents can create projects, inspect transcripts, render jobs, check status, and retrieve output files.MIT
- AlicenseCqualityDmaintenanceEnables AI agents to perform headless video editing through 35 tools for project creation, clip manipulation, rendering, quality control, and semantic search, all via JSON-RPC 2.0 over stdio.371MIT
- AlicenseNot gradedqualityCmaintenanceExposes 51 tools that let MCP clients open code-based videos as an interactive timeline and edit them directly: retyping on-video text, dragging numbers and colors in the drawing code, moving and muting sounds, and leaving notes on frames. Also covers image generation and exporting to MP4, WebM, GIF, PNG or a single frame with platform presets.4MIT
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.