Capture, buy and sync web motion from the terminal: the mvoom CLI
The CLI is the same engine without the chat: capture a piece by URL and selector, get the recipe as JSON, and pair a project so the components you buy arrive in the folder where you work. It is open source and has no engine logic inside — it talks to the service over the versioned HTTP contract.
mvoom auth stores the key you issued under Settings, pasted at a prompt — never on the command line, never in your shell history. mvoom capture <url> --piece ".hero" reads a piece and prints the recipe. mvoom connect pairs the current folder with your account, so a purchase from the chat, the MCP or the SDK lands here as files.
- 01Install
npm i -g @mvoom/cli (bun add -g works too).
- 02Authenticate
mvoom auth, paste the key from Settings → Terminal key.
- 03Capture
mvoom capture https://example.com --piece ".hero" — the recipe, as JSON when you pipe it.
- 04Connect
mvoom connect in your project. What you buy lands here.
- Recipes as JSON, scriptable
- A paired project folder that receives purchased components
- MIT, open source, auditable
Does the CLI use my free reads?
Yes — reads count the same wherever they come from: 2 a day without an account, 3 a day with a free account, more on a plan.
Where is the key stored?
In your user config, by mvoom auth. The service keeps only an HMAC of it; reissuing revokes the previous key on the spot.
Reading is free and needs no account. Everything above is what runs today — nothing here is a roadmap.
READ THE CLI DOCS →