Subframe has put about 310 MIT-licensed React animations behind a read-only MCP server that Claude Code, Cursor or Codex can search with no account. We tested it, and it does what the page says. The caveats are ordinary ones: it's React only, there's no repo to fork, and the code is still third-party code. Here's AI Lab Australia's read, and where we'd draw the line for clients.
Subframe has put about 310 MIT-licensed React animations behind a read-only MCP server that Claude Code, Cursor or Codex can search with no account. We tested it, and it does what the page says. The caveats are ordinary ones: it's React only, there's no repo to fork, and the code is still third-party code. Here's AI Lab Australia's read, and where we'd draw the line for clients.
Roman sent the link over with a short note: "We can recommend this." That's a claim we have to stand behind, so we read the page, the docs, the terms, the privacy policy, the DPA and the trust centre, and called the server ourselves.
Short version: the free library is good, honest and worth using in a React project, with a review step. The paid app behind it is a separate decision, and for client data it's not one we'd make yet.
Subframe Motion is a curated library of interactive UI animation examples. When we counted on 29 October, the page listed 310 of them. They're React components. Some use the Motion animation package (formerly Framer Motion) and some use WebGL shaders.
The animations aren't AI-generated. They're hand-built source code. The AI part is your own coding agent searching the library and adapting what it finds into your project.
The library launched on 22 October 2026, and 21 more examples landed on 27 October. So it's a week old. Keep that in mind.
The maker is Subframe, legally Atomic Design Inc of San Francisco, according to its terms of service. Its main product is a paid design tool and coding-agent canvas that outputs React and Tailwind. It's fair to read the free library as the front door to that paid app. That's not a criticism. It's worth knowing who's handing you the code, and why.
The delivery mechanism is the interesting bit. The library sits behind an MCP server. MCP is the standard plug-in protocol that lets AI agents call outside tools, and Subframe's MCP server docs say the motion tools are available without an account at mcp.subframe.com/motion/mcp.
We checked. Connecting, listing tools, searching and fetching an example all worked with no sign-in. The server has three tools, all marked read-only:
Nothing gets installed for you. The tool "writes no files", and each example tells you to keep its licence header and test it in your project.
What came back was better than we expected. Each example we pulled came with adapt notes, reduced-motion behaviour and its limitations. The built-in guidance is sensible, too: 100 to 200 ms for hovers and presses, exits about a third faster than entrances, and respect for prefers-reduced-motion. That's the kind of restraint most animation libraries skip.
We haven't independently tested the animations' quality or accessibility. The notes are good. Whether every example lives up to them is for your own testing to settle.
The page says "open-source React animations". Here's what that means in practice.
We sampled 112 examples through the MCP server, and all 112 were MIT-licensed. Most are Subframe's own work. Some are adapted from other MIT projects and say so. The shimmer button, for example, credits Magic UI, keeps Magic UI's MIT header and pins the upstream commit it came from. That's careful attribution.
What we didn't find is a repo. The source isn't in Subframe's public GitHub repository, and we found no other public copy. So the accurate description is "open licence, delivered from their server". You can use the code commercially as long as you keep the notice. You can't fork the library, watch its commit history or open a pull request against it.
For most teams that's fine. Just remember the server is the source of truth, and it belongs to someone else.
None of these is a reason to avoid it. All are reasons to use it properly.
It's React only. The code targets React 19. On React 18 with server rendering, the tool description says you need to move the inline style block into a stylesheet. As far as we can tell from the docs and tool schemas, there's nothing for Vue, Svelte or plain HTML and CSS, no animation generator and no Figma or Lottie export. If your Australian business runs on WordPress or Shopify themes without React, this isn't for you.
There's no forkable repo. Covered above. Copy what you use into your own codebase, so your site never depends on their server staying up.
Treat the code as third-party code. It's a remote server sending instructions and code into your agent's context. In principle, that's a supply-chain and prompt-injection surface. We saw nothing bad in what we received. That's a test result, not a guarantee.
Pin your dependencies. Most examples need only React. In our sample, 22 of 112 needed motion@12.0.5, and the WebGL ones need WebGL 1, with a static CSS fallback. Pin that version rather than taking whatever's latest.
Watch performance. Shader examples can be heavy on the GPU. The liquid chrome example says so itself. Test on real devices, not just your dev machine.
Your agent's searches go to a US company. What leaves your machine is the agent's search queries, which describe what you're building. Links carry utm_source=subframe-motion-mcp tracking. We found no separate privacy notice for the MCP server, so assume Subframe's general privacy policy applies. For a public marketing site, that's trivial. For an unannounced product, think about what your queries say.
We're not going to invent install commands. Each coding agent configures MCP servers its own way, so follow your client's documentation and Subframe's MCP docs. Here's the shape of the workflow the sources support.
Step 4 is the one people skip. Don't.
Different product, different risks. The library needs no account and returns code. The app holds your designs in Subframe's cloud. The facts, from Subframe's own pages:
For an Australian business, the US processing is the part to think about. If a client's designs or content include personal information, sending them overseas brings in APP 8, and you generally stay accountable for what the overseas recipient does with it. We walk through that in our guide to the Privacy Act and AI for Australian businesses.
The library: yes, with code review. In a React project, with a person reviewing the code before it's merged, we'd use it today. It's MIT-licensed, carefully attributed, read-only and well documented. A Sydney web team building a React marketing site gets well-behaved micro-interactions for nothing.
The paid app: not for client data yet. Not until there's a SOC 2 report, or at least the pentest and a subprocessor list we can read, plus a review against the Australian Privacy Act. That's not an accusation. It's the standard we'd apply to any vendor that holds client material offshore.
Hypothetical example: picture a five-person studio in Surry Hills building a React site for a physio clinic. Using the motion library to add a button press effect and a calm shader behind the headline is fine. The agent's searches describe a button and a background, and the code gets reviewed before merge. Moving the clinic's patient-facing pages and content into the paid app's cloud canvas is a different question, and one we'd want answered on paper first.
Is Subframe Motion free? Yes. The library is free and the motion MCP server needs no account. The paid Subframe app is separate, with Pro at US$20 per editor per month.
Is it really open source? The code is MIT-licensed, and all 112 examples we sampled carried that licence. But there's no public repo to fork. It's open-licensed code served from Subframe's server.
Does it work with Vue, Svelte or WordPress? Not as far as we can tell. It's React, targeting React 19. React 18 with server rendering needs the inline styles moved into a stylesheet.
Is it safe to let my agent pull code from it? It's read-only and returned clean code in our test. Treat it like any third-party snippet: review it, keep the header, pin motion, and no auto-run installs.
Does using it send my data overseas? The library sends your agent's search queries to Subframe, a US company. The paid app processes data in the United States, which matters under the Privacy Act if personal information is involved.
Subframe Motion is what it says it is: free, well-documented React animations your coding agent can search without signing up. The licensing is clean and the guidance is genuinely good.
Use it the way you'd use any code from a stranger, however polite: read it, pin it, keep the header, test it. And keep the free library and the paid app in separate boxes.
If your team in Sydney or anywhere in Australia is working out which AI coding tools are safe to bring into client work, our AI consulting team can help. Or get in touch and email info@ailabaustralia.com. We'll tell you straight whether it's worth doing.
Get expert guidance on implementing ai tools solutions for your Australian business
