MCP server
Use snapcn in your agent
Your agent searches the registry, reads a component's real props and plans the whole video from a one-line brief — then installs the components with the shadcn CLI.
- 1
Get your key
Every Pro plan includes one. Copy it from your account — it replaces
YOUR_KEYbelow. - 2
Add the server to your agent
One command in your project. Restart the session to pick it up.
claude mcp add snapcn -- npx -y @snapcn/mcp@latest SNAPCN_API_KEY=YOUR_KEYAdd --scope user before the name to have it in every project.
- 3
Ask for a video
Paste any prompt below. The agent picks the tool itself.
Plan a whole video
A one-line brief becomes beats, one component each, one install command and a TransitionSeries skeleton — once it has your real copy.
“Plan a 20-second launch video for this repo with snapcn. Dark mode.”
Find the component for a shot
Describe what the shot has to do. Get ranked components with their length, install command and, where written, when not to use them.
“Find a snapcn component that shows our CLI install command running in a terminal.”
Get a component's real props
The install command, its tunable props with defaults and ranges, and its frame budget — read off the registry, not guessed.
“Get text-reveal's props from snapcn, then add a headline scene that says “Ship faster”.”
Cut a screen recording into beats
Measures the chrome to crop, the frame each beat opens on and where to point the camera — off the file itself.
“Measure public/demo.mp4 with snapcn and plan a product demo around it.”
Look at a frame before you ship
Renders frames of your composition with your own Remotion CLI and hands the image back, so the agent sees what it wrote.
“Render frames 30 and 120 of the Video composition with snapcn and fix anything that looks wrong.”
Write chrome that matches
snapcn's motion, design and anti-slop rules, for the backdrops, cards and easing the agent writes itself.
“Read snapcn's design rules, then build a lower-third that matches the components.”
Good to know
- Runs locally
- Node 18 or newer. Previews and recording analysis use the Remotion CLI already in your project. The live registry is read first, with a copy bundled in the package as fallback.
- Your key
- Checked with snapcn.dev on the first call and every 15 minutes after. Delete it on your account and the server stops within that.
- Pro components
- Show up in search, marked Pro. Installing one also needs your key in
components.json— see your account.
Rather teach the agent than run a server? Install the agent skill.