{"slug": "fablecut-gets-its-own-studio-which-agents-can-actually-use", "title": "FableCut Gets its Own Studio Which Agents Can Actually Use", "summary": "A developer built FableCut Studio, a browser-based open-source video editor that lets AI agents edit an existing timeline directly through the Model Context Protocol rather than generating a new video from a prompt. Studio exposes 16 tools over remote MCP to clients including Claude Code, claude.ai, Cursor and ChatGPT, and keeps media files local while a relay carries only tool calls and requested frames. The latest release adds in-browser Whisper transcription, with one desktop CPU test transcribing 48 seconds of speech in 13 seconds.", "body_md": "I've been building FableCut for the past few months, and one thing I've wanted to explore is what video editing looks like when an AI agent can work directly with the editor instead of just generating instructions for a human to follow.\n\nThe idea is straightforward: open a video editor, connect an AI agent, describe the edit you want, and let the agent make changes to your actual project.\n\nThat project is now FableCut Studio.\n\n**Studio:** [https://studio.fablecut.space/](https://studio.fablecut.space/)\n\n**GitHub:** [https://github.com/ronak-create/FableCut](https://github.com/ronak-create/FableCut)\n\nHere's a quick demo of FableCut Studio in action:\n\nFableCut is an open-source video editor designed to work with AI agents through the Model Context Protocol (MCP).\n\nThe project started as a local editor that agents could control through `project.json` and MCP. The first version shipped on July 6, 2026.\n\nSince then, I've shipped 20 tagged versions, made 383 commits, and grown the project to 747 GitHub stars and 86 forks. It's available on npm as `fablecut`, is listed in the official MCP registry, and has been included in awesome-mcp-servers.\n\nThe original version required a local installation. Studio takes the same idea into the browser.\n\nYou open a link, load a project, connect an agent, and start editing.\n\nNo editor installation is required.\n\nMost AI video tools focus on generating a new video from a prompt. I wanted to explore something different: letting an agent work with an existing editing timeline.\n\nImagine giving an agent instructions like:\n\nThese tasks involve more than generating a video. The agent needs to understand the project, make targeted changes, and preserve the existing work.\n\nThat's the direction I've been building toward with FableCut.\n\nStudio runs at [https://studio.fablecut.space/](https://studio.fablecut.space/) and exposes 16 tools through remote MCP.\n\nDifferent clients can connect to it, including Claude Code, claude.ai, Cursor, ChatGPT, OpenCode, and other compatible MCP clients.\n\nThe connection process depends on the client. For example, claude.ai supports a custom connector, while Claude Code can connect using a command.\n\nOnce connected, the agent can call tools to inspect and modify the project. Those changes appear live in the editor.\n\nThere's also an Agent panel that lists tool calls, and you can pause the agent or issue a new link when needed.\n\nThe important part is that the agent isn't simply returning a list of suggestions. It's interacting with the actual editing project.\n\nIn Chromium-based browsers such as Chrome, Edge, Brave, and Arc, Studio can work with a folder on your disk and save `project.json` there.\n\nFirefox and Safari use browser storage for projects, with a download option for exporting the project as a ZIP.\n\nYour video clips are not uploaded to Studio's server.\n\nThere is one important distinction: the remote MCP relay carries tool calls and their results, including project information and any frames the agent requests. It does not receive the media files themselves.\n\nI think being clear about this boundary matters when building AI tools that work with local files.\n\nThe latest release adds transcription and text-based editing to Studio.\n\nThese features make it possible to perform common editing tasks using the words spoken in a video rather than manually searching through the timeline.\n\nStudio uses Whisper to transcribe audio in the browser.\n\nThe model is approximately 77 MB and downloads the first time transcription is used. After that initial download, transcription runs on the device.\n\nIn one desktop CPU test, 48 seconds of speech took 13 seconds to transcribe.\n\nThat is a useful result for a feature that doesn't require uploading the audio to a transcription service.\n\nOnce a transcript is available, you can interact with the words directly.\n\nYou can click a word to jump to its position, select words and delete them, or search for a phrase and cut every occurrence in one operation.\n\nThe cuts are grouped into a single undo step, making it easier to experiment without losing control of the edit.\n\nFor example, if a recording contains several repetitions of the same phrase, you can remove those repetitions without manually locating each one on the timeline.\n\nStudio can generate captions from the transcript and time them word by word.\n\nThe available styles include:\n\nCaption layouts also adapt to the canvas dimensions, so vertical videos can use narrower lines than landscape videos.\n\nSRT and VTT import and export are supported as well.\n\nStudio can automatically remove pauses from a recording.\n\nThis is useful for talking-head videos, tutorials, interviews, and short-form content where long pauses can make the final video feel slow.\n\nOne limitation worth mentioning: Whisper generally drops filler words such as \"um\" and \"uh\". Silence removal and transcript-based editing serve different purposes, so filler removal is better handled through the silence-removal workflow rather than assuming every filler will appear in the transcript.\n\nThe transcription and editing features aren't limited to manual use in the browser.\n\nAgents can use tools such as `fablecut_transcribe`, `fablecut_captions`, and `fablecut_silence`.\n\nThat means a prompt like \"caption this reel in highlight style\" can become an actual editing operation instead of a tutorial explaining how to create captions.\n\nThis is where I think MCP becomes particularly useful: it gives an agent a structured way to interact with an existing application.\n\nThe project has grown well beyond basic timeline operations.\n\nOver the last several releases, I've added:\n\nThese features matter because an agent needs a real editing environment to work with. The more capable the editor becomes, the more useful its tools can be.\n\nAgents can also inspect frames, measure color grades using scopes, and save project versions before substantial edits. The editor respects track locks rather than treating the entire timeline as freely editable.\n\nStudio encodes exports in the browser, supporting formats and codecs including H.264, HEVC, VP9, and AV1, with supported audio options.\n\nWebCodecs has also helped make exports substantially faster. In v1.16, the project introduced an export path measured at roughly five times faster than the previous implementation.\n\nFor an editing application, performance matters just as much as the AI integration. An agent might make the right changes, but the workflow is still frustrating if exporting the result takes too long.\n\nStudio isn't the only way to use FableCut.\n\nYou can install the local version through npm:\n\n```\nnpx -y fablecut\n```\n\nThe local version exposes 21 MCP tools and supports additional machine-local workflows, including FFmpeg-dependent features.\n\nThis is a useful option if you prefer a local agent setup or need functionality that isn't available in the browser version.\n\nI've added a demo project containing skate clips, a music track, and an initial edit. You don't need to prepare your own footage just to see how the editor works.\n\nYou can also explore the source code on [GitHub](https://github.com/ronak-create/FableCut).\n\nFableCut is released under the MIT license.\n\nI'm continuing to build FableCut around the idea that AI agents should be able to work inside real creative applications, with structured tools and visible results.\n\nThere's still plenty to improve, but the latest release brings the project closer to a workflow where an agent can help with the tedious parts of editing while the editor remains the place where the actual project lives.\n\nIf you try it, I'd genuinely like to hear what works, what breaks, and what you'd want an agent to be able to do next.", "url": "https://wpnews.pro/news/fablecut-gets-its-own-studio-which-agents-can-actually-use", "canonical_source": "https://dev.to/ronak_parmar_033c50d168b5/i-built-a-video-editor-that-ai-agents-can-actually-use-1kcd", "published_at": "2026-10-26 18:33:57+00:00", "updated_at": "2026-10-26 18:43:00.901421+00:00", "lang": "en", "topics": ["ai-agents", "agent-protocols", "ai-tools", "generative-ai", "developer-tools"], "entities": ["FableCut", "FableCut Studio", "Model Context Protocol", "Claude Code", "claude.ai", "Cursor", "ChatGPT", "Whisper"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/fablecut-gets-its-own-studio-which-agents-can-actually-use", "markdown": "https://wpnews.pro/news/fablecut-gets-its-own-studio-which-agents-can-actually-use.md", "text": "https://wpnews.pro/news/fablecut-gets-its-own-studio-which-agents-can-actually-use.txt", "jsonld": "https://wpnews.pro/news/fablecut-gets-its-own-studio-which-agents-can-actually-use.jsonld"}}