FableCut: Open-Source Browser Video Editor for AI Agents (2026)

Ever wanted your AI agent to edit a video for you? So I just made it happen.

So I dropped six raw clips into a folder, told Claude Code to “cut these to the beat markers, add a teal-orange grade, and put word-pop captions” — and watched the timeline rebuild itself live in my browser. No Premiere. No cloud service. Just a node server.js and an MCP connection.

So what’s the project? It’s called FableCut — a zero-dependency browser video editor that exposes its entire timeline as JSON. Also, any MCP-capable agent can manipulate it. It’s MIT-licensed, sits at 268 stars, and was only released four days ago. But honestly? The concept is bigger than the star count.

Quick Verdict

Honestly? FableCut is not a Premiere replacement. So it’s a programmatic timeline that your agent can drive — cut clips, add transitions, apply color grades, generate captions, analyze reference videos for beats and energy. The JSON project file IS the API. Plus it runs in the browser with a live-reload UI, so you watch every edit happen in real time.

Best for: developers who already use AI coding agents and want to extend them into video. Content creators who need rapid batch processing. Anyone who’s ever thought “I wish my agent could do this for me.”

Not for: professional colorists, multi-cam editors, or anyone needing audio multitrack mixing. This is an early-stage agent tool, not a DaVinci Resolve competitor.

What Makes FableCut Different?

But here’s the thing. Most “AI video” tools work one of two ways. Either they’re a cloud service with an opaque API (RunwayML, Canva) where you send footage in and get a rendered video back — zero visibility into what happened. Or they’re a desktop app with no programmatic interface at all (Premiere, DaVinci).

But FableCut takes a third approach: the project file IS the interface.

And the entire timeline — clips, tracks, effects, keyframes, markers — lives in a JSON structure. Plus your agent can read it, patch it with diffs, add a filter, move clips around, and commit changes. The browser UI subscribes to file changes and live-reloads. So you get:

• MCP interface: claude mcp add and your Claude Code instance can drive the editor
• REST API: POST /api/project with a JSON patch, GET /api/timeline to inspect state
• Plain file writes: Drop a modified project.json and watch the browser update

Still, no other open-source video editor works this way. Not even close.

How I Tested It: Agent Edits Video, I Watch

So I set up FableCut on my MacBook Air M3 — took about 30 seconds (git clone, node server.js). Then I registered the MCP server:

claude mcp add -s user fablecut -- node "/Users/githubdigger/FableCut/mcp-server.js"

Then I grabbed six clips from a test shoot: a wide shot, two close-ups, three B-roll clips. Then I dropped them in a folder and opened Claude Code to type:

“Load all clips from ~/test-footage/. Analyze the reference clip’s beat structure. Create a 30-second edit cutting on the beat. Apply a teal-orange color grade. Add ‘pop’ style captions to the first three cuts.”

Then I watched the timeline build itself in my browser — clips snapping into place, cuts aligning to detected beats, captions appearing on keyframes. And the whole thing took about 14 seconds from prompt to rendered preview.

So here’s what I learned from that session:

• Beat detection worked well — FableCut analyzed the reference clip, found a 124 BPM tempo, and placed cuts at measure boundaries. The timing felt natural.
• The teal-orange grade was aggressive — 100% saturation on the LUT. I had to ask the agent to dial it back to 70%. A one-line instruction change.
• Captions needed manual tweaking — the word-pop effect generates by phrase peaks, not word boundaries. Some captions were half a second off. Fixable, but not perfect.
• JSON patching is fast — the diff-based approach meant edits took milliseconds, even on a 50MB project with 12 clips. No full reloads.

So it’s not flawless. But the key thing is: I could iterate by telling the agent what to change. That’s the whole point.

Core Features

But the reference analysis is the feature that surprised me most. I fed it a 30-second ad spot — a fast-paced product demo — and it returned shot boundaries, average energy per segment, and the BPM of the background track (132 BPM). Now that data feeds directly into the JSON timeline so your agent can make editorial decisions based on actual video rhythm, not guesswork.

Quick Start

Still, getting FableCut running is dead simple. Three steps and you’re editing video with an agent.

Step 1: Clone and start the server

git clone https://github.com/ronak-create/FableCut.git
cd FableCut
node server.js

Now the UI opens at http://localhost:7777. You’ll see a blank timeline. Don’t close it.

Step 2: Register the MCP server

claude mcp add -s user fablecut -- node "/absolute/path/to/FableCut/mcp-server.js"

Now replace the path with your actual clone location. That’s it — your Claude Code instance now has video editing tools available. If you want to see what those MCP tool calls look like under the hood, MCPsnoop is a great debugging companion.

Step 3: Call it from your agent

# Or via REST API directly
curl -X POST http://localhost:7777/api/project \
  -H "Content-Type: application/json" \
  -d '{"action": "addClip", "path": "/clips/demo.mp4", "track": 1, "position": 0}'

Now from there you can ask your agent anything — “cut these clips on the beat”, “add a blur transition between clip 2 and 3”, “generate captions for the whole timeline.”

Running FableCut on a VPS

For a shared team setup or a 24/7 agent-accessible server, deploy FableCut to a cheap VPS. So DigitalOcean’s $6/mo droplet handles it easily — Node.js + optional ffmpeg for server-side rendering. (affiliate link)

Then install PM2 to keep it alive:

npm install -g pm2
pm2 start server.js --name fablecut
pm2 save
pm2 startup

That’s it. Now point your MCP config at the server, and any agent in your team can talk to the same timeline. Vultr and Hostinger are solid alternatives if DO isn’t available in your region.

FableCut vs The Alternatives

Here’s how it stacks up against the tools you’re probably using now:

Still, the clear gap is export. FableCut renders in the browser, so the agent can’t trigger a headless export yet. Still, the developer is working on a CLI export command. For now you still click “Export” yourself.

Who Should Use FableCut

• AI developers who want to extend their agent’s capabilities beyond text/code. If you already use tools like Repomix to pack codebases for AI agents, FableCut is a natural next step into creative work.
• Content creators producing fast-turnaround shorts — product demos, social clips, reaction videos. Batch processing with agent instructions beats clicking in a timeline.
• Teams needing programmatic video — think automated ad variants, event recaps, or training videos generated from a script. One JSON template, one agent command, done.
• Anyone curious about agent creative tools — this is one of the first projects that genuinely demonstrates an agent doing visual creative work, not just writing markdown.

Limitations

But let me be upfront. FableCut is 4 days old. That means:

• Small community — 268 stars, 10 forks. You’re an early adopter.
• Export requires a browser — the agent can build the timeline but can’t trigger the render. Open issue on GitHub.
• Caption timing isn’t perfect — phrase-based rather than word-accurate. Manual adjustment still needed.
• No audio multitrack — single audio track only. Fine for cuts and voiceovers, not for complex sound design.
• Limited codec support — browser-native only. No ProRes, no DNxHD.

Even so, for an MIT project that’s been public for less than a week? The direction is right. The MCP integration is what sets it apart — that’s not going to change as the project matures.

Bottom Line

So here’s my take. Look, FableCut is the first open-source video editor designed for AI agent control. Plus the MCP integration works, the JSON timeline approach is clever, and watching an agent build an edit in real time is genuinely impressive. Still, it’s rough in places — export needs work, captions need tuning — but the core concept is solid.

Still, if you use AI agents and have ever wanted them to do video work, this is the project to watch. Yet I’d give it a month of dev before it’s ready for serious production. But for experimenting today? It already delivers.

So try FableCut on your machine — git clone, node server.js, and see what your agent can do.