Mount a measured motion mechanism on your own DOM: the mvoom SDK
The component you buy from mvoom is self-contained and brings its own mounting code. The SDK is the other path: you already have the markup — a hero, a grid, a list — and you want the measured mechanism to run on it without generating files. Give it a recipe and an element; it mounts, interprets the trigger, and hands you back a function to stop.
A recipe is the measured mechanism as data: properties, keyframes, duration, curve, delay and trigger — the VUI Spec that the API, the CLI and the MCP return. montar(recipe, element) mounts it with the Web Animations API. A viewport trigger becomes an IntersectionObserver; a scroll-linked one becomes a scroll listener mapped to the measured range; hover and click become listeners. Nothing is approximated with a timer.
There are adapters for React (useMvoom returns a ref) and Vue (useMvoom takes a ref), in their own entry points so a plain-DOM project pulls neither. The core has no dependencies and no framework.
An agent that reads a piece through the MCP and wants to apply its mechanism to the markup it already generated. A design system that stores mechanisms as data. A product that mounts the same measured entrance on a hundred cards without shipping a hundred components.
- 01Install
npm i @mvoom/sdk. Import montar, or useMvoom from @mvoom/sdk/react or @mvoom/sdk/vue.
- 02Get a recipe
From a read in the chat, the CLI (mvoom capture --json), or the MCP.
- 03Mount it
const stop = montar(recipe, element). Call stop() when the element goes away.
- A zero-dependency runtime for measured recipes
- React and Vue adapters in separate entry points
- Triggers interpreted: viewport, scroll range, hover, click
- MIT, open source, no engine logic inside
Is the SDK an HTTP client for the API?
No. The SDK runs recipes; the CLI and the MCP talk to the service over the versioned HTTP contract. If you build your own client, the contract is plain JSON over HTTPS.
Does it need React?
No. The core is framework-free; React and Vue adapters are optional entry points.
Reading is free and needs no account. Everything above is what runs today — nothing here is a roadmap.
READ THE SDK DOCS →