Ship the feature.
It demos itself.
Claude Code drives your running app, records it, narrates it, and hands you a public link. One command, every time you ship — your product documents itself.
From Commit to Shareable Demo
One command after you ship. Vidmatic does the other four steps.
You ship
Run /mcp__vidmatic__record in Claude Code. It reads your recent commits to work out what is actually worth showing.
It records
Playwright drives your running app through the real journey — your actual UI, not a mock screen or a slide.
It narrates
A script is written for what was captured and rendered in an AI voice, timed to the recording that actually happened.
You get a link
The video is encoded and published. Paste the public URL into Slack, a PR, or a release note.
Every Release Ships With Its Demo
Not the demo nobody had time to record. The one that recorded itself.
Nothing To Install
One claude mcp add line, once per machine. No pip install, no local ffmpeg, no test harness to commit — recording, narration and encoding all run on Vidmatic.
Demos That Match The Build
Each demo is captured from your app as it is the day you ship it, so what people watch is what your users will actually see.
A Link For People Who Never Open Your Repo
Support, sales and your PM get the two-minute version, narration and transcript attached. No screen-share to schedule.
Two Commands, One of Them Once
One connects Claude Code to Vidmatic. The other is the one you run every time you ship.
- 1Connect Claude Code — once per machine
claude mcp add --transport http --scope user vidmatic …Abbreviated — Vidmatic builds the real, paste-ready line with your key already in it.
- 2Then, whenever you ship something
/mcp__vidmatic__recordRecords your real UI, narrates it, returns a public link.
The same connection also serves /mcp__vidmatic__audit_ux — a narrated UX critique of any live page, circling each finding on screen. Nothing extra to install.
Built For Your Workflow
Start with demos. The same recording pipeline files bug reports and tickets too.