Remotion components your AI agent can install
Kuchi's component library has 178 Remotion components for launch videos: kinetic type, captions, phone and UI screens, AI chat windows, cursors, logo lockups and transitions. Each one is a source file in the shadcn registry format, so it is copied into your project and becomes your code to edit, not a dependency you import.
Because the registry is plain JSON on the web, an AI coding agent can find the right component, read its source and install it without you opening a browser. There are three ways to wire that up.
1. Through the Kuchi MCP server
If your agent already has the Kuchi MCP server connected, it has two component tools:
kuchi_list_componentslists the components, with a search and a category filter.kuchi_get_componentreturns one component's description, dependencies, install command, usage notes and the full source of its files.
This is the route the Kuchi workflow uses. While building a remake, the agent checks each shot of its blueprint against the list, and where a component fits (a kinetic type title, a chat prompt typing itself, a cursor click) it installs that component and passes your text, colours and assets in its props.
Find a Kuchi component for word-by-word captions, show me its props, then install it and add it to my intro scene with my tagline.2. With the shadcn CLI
Every component has its own registry URL. Your agent, or you, can install one in a Remotion project with a single command:
npx shadcn@latest add https://kuchi.kalarislabs.com/r/text-reveal.jsonIts dependencies come with it: other Kuchi components it builds on and npm packages such as remotion. The whole index is at /r/registry.json.
3. Through the shadcn MCP server
The shadcn CLI ships its own MCP server, which lets an agent browse, search and install from any registry you name. Add Kuchi as the @kuchi registry in your project's components.json:
{
"registries": {
"@kuchi": "https://kuchi.kalarislabs.com/r/{name}.json"
}
}Then set up the shadcn MCP server for your client. The --client option takes claude, cursor, vscode, codex or opencode:
npx shadcn@latest mcp init --client claudeYour agent can now ask for things like "search @kuchi for captions" or "add @kuchi/word-captions". The same namespace works on the command line:
npx shadcn@latest search @kuchi -q caption
npx shadcn@latest add @kuchi/word-captionsWhich route to use
| Route | Best when |
|---|---|
| Kuchi MCP | You are remaking a launch video: the agent picks components shot by shot from the blueprint, alongside the breakdown and plan tools. |
| shadcn CLI | You know which component you want, or you are adding one by hand. |
| shadcn MCP | Your project already uses shadcn registries and you want Kuchi beside them in the same agent tools. |
Using a component in a scene
Components render inside a Remotion composition. Put each one in a Sequence timed to its shot, and pass your own words and colours. This is how Kuchi's own launch film reveals a list of words, one per second, with letters that settle into the film's ink colour:
import { AbsoluteFill, Sequence } from "remotion";
import { ShaderTextReveal } from "@/components/kuchi/shader-text-reveal";
export const Features = () => (
<AbsoluteFill style={{ background: "#FFFFFF" }}>
<Sequence from={0} durationInFrames={180}>
<ShaderTextReveal
text={"Kinetic type\nCaptions\nUI screens"}
fontFamily="Inter Tight"
fontWeight={600}
wordDuration={32}
/>
</Sequence>
</AbsoluteFill>
);Transitions work the same way. A component such as Dot Bloom exports its length and the frame where it covers the screen, so you cut between your two shots underneath it on exactly that frame.
Tips
- Give a component a background. A few draw on a transparent layer and render black without one.
- Many components were measured off real launch videos and run a set number of frames. Read the exported constants (often
*_FRAMES) before you size the shot. - Pass the brand theme once. Components that take
themeormodeaccept the same colours, so one constant keeps a whole film consistent. - Edit the copy you installed. It is your source now: change a shadow, a colour ramp or an easing to fit your brand.
Questions
Do Kuchi components need Remotion?
Yes. They are Remotion components and render inside a Remotion composition. Install them into a Remotion project.
Are the components installed as a package?
No. Like shadcn/ui, each component is copied into your project as source, so you can change anything in it.
Do I need an account or API key for the registry?
No. The registry is public JSON at kuchi.kalarislabs.com/r, and the MCP servers need no sign-in.
Can my agent search the components?
Yes: kuchi_list_components over the Kuchi MCP server, or the shadcn MCP server and npx shadcn search once @kuchi is in components.json.
How do I preview a component before installing it?
Every component has a page with a video preview, its props and its source at kuchi.kalarislabs.com/components.

