Give Claude, Cursor or Codex a motion decompiler: the mvoom MCP
An agent that can read a site's motion and drop a measured component into your project is a different kind of assistant. The mvoom MCP gives it exactly that — with one rule that is the whole design: the tools that read and quote have no side effects and run freely; the one that spends money stops and waits for a human to type y.
mvoom_discover_page lists what moves on a page and names the pieces. mvoom_inspect_component measures one piece and returns the recipe and the quote. mvoom_get_wallet_balance lets the agent ask before it tries. mvoom_purchase_and_inject buys the component and writes the files into the folder you paired — and it cannot run without your signature in the terminal.
Ceilings live on the server: a per-purchase ceiling and a monthly ceiling, in credits, set under Settings. Below them a purchase goes through; above them the connector freezes and asks. A patched client cannot walk past a server-side ceiling.
Run mvoom connect in the project folder once: it pairs the folder with your account. From then on, when the agent buys a piece, the files land there — component, recipes, motion, tokens, preview, README — and the agent can wire them in. The measurement is summarised for the model (a brief per piece, detail on demand), so it does not flood the context window with a spec.
- 01Install
npm i -g @mvoom/mcp, then add the mvoom-mcp binary to your client's MCP configuration (Claude Desktop, Claude Code, Cursor, Codex).
- 02Issue a key
Settings → Terminal key. It is shown once; the MCP reads it from mvoom auth.
- 03Pair a project
mvoom connect inside the project folder. Purchases land there.
- 04Ask
"Read the hero on this URL and add its entrance to our landing." The agent discovers, inspects, quotes — and asks you before it buys.
- Four MCP tools, MIT, open source, no engine logic inside
- Server-side spending ceilings you set in credits
- Components delivered into your paired project folder
Can the agent spend my money by itself?
Only below the ceilings you set, and never a purchase above them: the connector stops and asks for y in your terminal. Set both ceilings to zero and nothing is bought without you.
Which clients work?
Any MCP client over stdio: Claude Desktop, Claude Code, Cursor, Codex, Windsurf and the rest. The MCP is a small Node binary.
Does the model see the page's content?
No. The measurement is sanitised before it exists; the model receives mechanics and a brief. There is also an optional local-model adapter for adapting a piece on your machine, off by default.
Reading is free and needs no account. Everything above is what runs today — nothing here is a roadmap.
READ THE MCP DOCS →