Live demo of weaverclip_search_transcript.
{ "mcpServers": { "weaverclip": { "command": "npx", "args": ["-y","weaverclip-mcp"] } } }WeaverClip for developers
WeaverClip uploads long screen recordings to private cloud storage while you record. Each segment is verified before the local copy is removed. Later, search the transcript or turn the moment where you solved the problem into a captioned clip.
Already recorded? Import a video for captionsThis example session kept 18.6 GB off the Mac after every segment was verified.
Why developers use it
WeaverClip is a recording vault first. Coding sessions are one type of recording that benefits from the same upload, verification, transcript, and clipping pipeline.
OBS saves short recording segments. The helper uploads each one while you keep working, and a local segment is removed only after the cloud copy passes a byte-count and checksum check. If the connection fails, the file stays and retries.
Processed recordings get one word-timed transcript. Search for the method name, the error message, or the decision you explained instead of watching a two-hour timeline.
Choose a suggested moment or set exact start and end times. WeaverClip renders a captioned MP4 in vertical, landscape, or square — without modifying the source recording.
The MCP connection lets Claude, Codex, or another client list sessions, read transcripts and timecodes, and create clip decisions. Raw video never travels through the MCP connection.
Coding sessions that fit
Record the steps that break the feature, then share a captioned clip with the fix instead of a long written repro.
Explain what changed and why while the code is in front of you. Reviewers can watch the exact screen instead of reading a wall of comments.
Keep the full session in private storage, then clip the parts the team needs for documentation or follow-up.
Record once, search the transcript later, and export the segments you actually publish.
Capture the whiteboard and the code so the decision survives the meeting and is easy to find months later.
Let reviewers watch the exact screen instead of parsing a text description of a visual problem.
How it works
Use the built-in WeaverClip recorder, the WeaverClip OBS profile, or import an MKV, MP4, MOV, or M4V recording you already made.
Short segments go to your private cloud storage as OBS keeps recording. You do not wait for the session to end.
The byte count and MD5 checksum must match the local file before WeaverClip removes it from your disk.
Choose the footage to process. Transcripts, captions, and clip suggestions use their own hour allowance, separate from storage. Rendered clips are MP4 files you review and download.
What WeaverClip moves
Each recording segment uploads to private storage, passes a byte-count and checksum check, and only then can the local copy be removed. Imported videos get the same verified treatment.
What stays on your machine
WeaverClip is not a second hard drive. It does not sync code repositories, node_modules, Docker images, build caches, or project folders. Those stay where your tools expect them. If a recording explains the code, WeaverClip stores the recording; the code stays in git.
MCP editing access
Connect Claude, Codex, or another MCP client to list recording sessions, read transcripts and exact timecodes, add markers, and create clip decisions. The finished clip renders exactly like one you create yourself.
Use the WeaverClip MCP to list my newest recording sessions.
Open the editing manifest for the session where I explain the auth fix.
Find the exact start and end timecodes for that explanation and show them to me.
Do not create a clip until I approve the timecodes.Plans and limits
Every plan states exactly how much footage you can store, how much can get transcripts and clip suggestions, how many clips you can render, and when source recordings delete automatically.
$0no monthly charge
$15per month
$29per month
$119per month
Uploading and storing footage never uses transcript hours. You choose which recording or time range gets processed, and only successfully processed source minutes count. Paid storage above the included amount is billed as overage, and uploads pause at twice the included storage on paid plans.
Developer questions
Free includes 5 GB of storage, 1 hour of source footage for transcripts and captions, and 3 watermarked renders. No card required.
Every vault table on this site shows storage in GB (the truth) and hours at 6 Mbps (the intuition). The asterisk is not a footnote to hide behind — it's the promise that we state the vault in bytes and the hour guide at a single, documented bitrate, plus the table to translate your actual OBS settings in seconds. A 2-hour 1080p60 Valorant VOD at 12 Mbps is 10.8 GB, not 5.4 GB. The “Free 10 GB” you bought holds one of those, not two. The same vault at 6 Mbps sermons holds two. If we only said “~3 hours” you'd buy the wrong plan and blame us at 2am when OBS says “upload paused.” So we show both: the vault in GB, the hour guide at 6 Mbps, and the four-row table (5 Mbps ~2.25 GB/h, 6 Mbps ~2.7 GB/h, 12 Mbps ~5.4 GB/h, 25 Mbps ~11.25 GB/h) so you can translate before you record. Hard limit is 2× vault — Creator 75→150 GB, Pro 150→300 GB, Studio 1500→3000 GB — uploads pause there, files stay on your Mac and retry with backoff. Nothing is deleted to make room. Overage is linear $0.04/GB-month, transcript never bills overage. That's the nuance that makes a 24h subathon at 12 Mbps (~129 GB) fit Studio 1.5 TB with headroom, while a 2h sermon at 6 Mbps fits Free 10 GB with 1.9 GB left. We reuse the same lib/product/calc.ts (gbPerHour, planFit, overageCost, clipYield) on every page, so a future $15→$16 change is one JSON edit, not 25 find-replaces. That's top 0.005% system thinking, not just pretty pages.