FableCut
Related Servers
Alternatives to FableCut
- AlicenseNot gradedqualityDmaintenanceAn async video generation MCP server with multi-provider support. Currently in skeleton phase with stub implementations, it will eventually enable video generation through providers like Veo 3.1, Grok Imagine Video, and Sora 2 Pro.MIT
- AlicenseAqualityCmaintenanceMakes Claude a real operator for Adobe Premiere Pro 2025, providing 59 tools to control projects, timelines, media, exports, and even create cinematic intros with beat detection and style presets.59MIT
- AlicenseBqualityAmaintenanceLocal MCP server that uses Playwright browser automation to enable Claude Code to generate images, create variations, expand, and remove backgrounds via Adobe Firefly, requiring manual sign-in once.1112 npmMIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceAI-native timeline editor for short-form video. Your agent cuts, captions, adds motion graphics and renders against a real, editable timeline over MCP — not a render queue. Human-in-the-loop by design: it calls request_review and waits while you supervise in a browser. Local-first and AGPL; your footage never leaves your machine.1AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceAn agentic AI video editor for Claude. It enables editing real video through MCP: cutting, captioning, reframing, scoring, and exporting finished MP4s from actual footage.MIT
- FlicenseBqualityAmaintenanceSource-available, local-first AI video editor — an MCP server over ffmpeg, whisper, and OpenTimelineIO132610 PyPI4-
- AlicenseNot gradedqualityBmaintenanceA real video editor for AI agents, served over MCP, enabling journaled timeline editing, rendering via FFmpeg/MLT, and deterministic CLI operation.1MIT
- AlicenseAqualityBmaintenanceGive any MCP client a real video editor — 32 typed tools over ffmpeg, Whisper and MediaPipe, plus an optional local UI with a drag-and-drop timeline.38MIT
- FlicenseNot gradedqualityBmaintenanceEnables prompt-driven video editing in Adobe Premiere Pro, allowing Claude to transcribe footage, decide cuts, build motion graphics, and assemble timelines via natural language.-
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes (import, export, denoise, duck, normalize, analyze, docs, status). The only real overlap is get_project / set_project / patch_project, which all touch the same resource, but the descriptions explicitly differentiate them (read vs. full replace vs. incremental patch with a recommended workflow), so confusion is limited.
Every tool uses the same fablecut_ prefix and snake_case verb_noun pattern (patch_project, get_project, import_media, normalize_audio, auto_duck, analyze_reference, encode_profiles). Nouns like docs and status are rare but readable deviations that don't break the predictable scheme.
12 tools is well within the ideal range and each earns its place — project read/write/patch, media import, export, three distinct audio processors, reference analysis, and support tools. No filler and no obvious redundancy.
The surface covers the full editing lifecycle: read/replace/patch the document, import media, apply detailed timeline and audio edits (via a rich op set), process audio, analyze references, and export. Support tools (docs, encode_profiles, status) close the loop, leaving no major workflow dead ends.