Somebody handed Claude a timeline and a 1911 art heist, and honestly the heist is the least interesting part.
The interesting part is the two lessons buried under the demo. ngl they read like a design doc every big MCP server should steal from.
ok so what did they actually build
A builder posted on r/mcp about AskEditor, a video editor that Claude drives over MCP. For the demo they gave it one true story, the guy who stole the Mona Lisa in 1911, and Claude wrote the script, did the voice and dropped 21 animated shots on a timeline with music and captions.
Then the human fixed a couple of shots by hand. No re-prompting the whole video.
The product site fills in the rest. You paste one line into Claude or ChatGPT, a plugin installs itself and the editor opens beside the chat. Any other agent connects through MCP. Every cut, caption and graphic the agent makes is its own clip you can move, trim or retype. There's also a Mac beta that edits the Final Cut Pro project you have open, and it can post the finished video to six networks, YouTube included.
The builder says it was made mostly with Claude Code. so Claude built the thing Claude now uses to make videos. it's giving ouroboros.
Lesson one: they ended up with around 200 tools "and that just eats the context." So now Claude only sees the basic editing tools, and the rest sit behind skills it loads when it needs them.
Say you ask for "trim the intro and add captions." Claude doesn't need the voice generator, the music picker or the motion graphics tools in its head for that. Loading every definition on every turn is paying rent on rooms nobody's in.
hot take: this is the most underrated problem in MCP right now. Everyone's racing to ship more tools, and every definition you add is something the model reads before it does anything at all. imo the right default is a tiny visible surface and everything else on demand.
It's the same instinct behind MewCP's gateway, which shows a client four tools (search, get_schema, list_accounts, call_tool) however many apps you've connected. The agent searches for what it needs, reads that one schema and calls it. Different mechanism from AskEditor's skills, same idea: don't make the model read the whole catalog to do one thing.
approve the money, not the edits
Lesson two, and the one I'd tattoo on every agent builder. Anything that costs money (voice, music) needs a yes from the person first. Claude asks, you approve in the editor, it carries on. For bigger jobs you approve a budget once.
The site shows what that looks like. Ask for a whole video and it starts as a plan.md with every step in order, what it costs and where it waits for your yes. Their example quotes 705 credits at most before step 1, and the run ends up spending 480. Edits on the timeline never use credits.
One commenter on the thread put it better than I can: "undoing a shot is cheap, a voice bill isn't."
That's the whole framework fr. Reversible stuff just runs. Stuff you can't take back waits for a human. imo a lot of agent setups get this backwards, they either ask permission for every tiny thing (so you stop reading and just smash approve) or they ask for nothing and you find out from your card statement.
The same split applies way outside video. If your agent touches real apps, MewCP lets you switch off actions per agent, like letting it read and send but not delete, and anything you switch off is stopped before it reaches the app. That's a hard no rather than an "ask me first", so it sits next to an approval step like AskEditor's instead of replacing it.
the shared timeline is kinda the sneaky win
A commenter asked the good question: when you fix a shot by hand, how does Claude even find out?
The builder's answer is that it just re-reads. The timeline is one shared doc and both the hand edits and Claude's tool calls write to it, so on its next turn Claude sees whatever you trimmed or moved. No diff yet. There's a revision number on it, so if the editor tries to save over a newer version Claude just wrote, it gets a conflict instead of wiping Claude's change.
my read: this is the right first version and also the thing that's gonna hurt first. Re-reading the whole timeline every turn is simple and hard to get wrong. But on a long project that's a lot of context spent re-learning what changed, which is lowkey the exact problem lesson one was trying to fix lol.
Another commenter described their own design board, where every change is tagged with who made it, person or agent, so undo only rolls back your own. The builder said they liked the idea. Same tbh. Once humans and agents edit the same file, "who did this" stops being a nice-to-have.
stuff we still don't know
This is one Reddit post with 16 points and five comments, plus the product's own website. Nobody independent has tested it in anything we found, me included.
- The thread doesn't say how much context the skills trick actually saves. "Eats the context" is a vibe, not a number.
- A commenter asked whether the budget approval resets per project or lasts the whole session. No answer in the thread when we read it.
- The site's pricing card says your first job is free with no watermark, and its FAQ says your first video is free with a watermark. Tiny thing but one of them is wrong.
Still, for a 16-point post it's a better MCP design write-up than most launch blogs. The video is the demo, the tool loading and the money gate are the takeaways.
where this came from