Show HN: I gave my video editor an MCP server so Claude can edit videos for me

A Show HN submission points to shorz.ai with the claim that the builder wired an MCP server into a video editor so Claude can drive edits. The HN thread is item 49175711 and sits at 6 points with 0 comments.

The core mechanic is **MCP** as the control surface: instead of a closed UI-only editor, the product exposes tools an agent can call so **Claude** can instruct cuts, arrangement, and other edit operations through that protocol rather than only through human mouse work.

For engineers building agent-native products, this is a concrete pattern—treat a heavy desktop-class app as a tool host, not only as a human UI. If the editor’s operations are addressable over **MCP**, the same model that writes code or plans tasks can also own a slice of the post-production loop without a custom one-off plugin language for each agent vendor.

On the market side, the post is framed against the **Claude / Codex / Fable** conversation on HN: agent tooling is spreading past IDEs into creative software. Shorz is presenting early traction as a demo, not as a crowded benchmark race—6 points and no discussion yet—so the signal is product shape more than adoption numbers.

What to watch next is whether more editors ship first-class **MCP** (or equivalent) surfaces, and whether agent-driven edits hold up on real timelines without constant human babysitting. If you build video or creative tooling, the practical question is which operations you expose as tools and how you scope permissions so an agent can help without wrecking a project.