What Sora UI is, how the copy-paste component model works, AI & MCP support, and why it's built for React, Motion, GSAP, and Tailwind CSS.
Sora UI is a distribution of React components built with Tailwind CSS and Motion, based on the shadcn registry and inspired by shadcn/ui and Magic UI. Our goal is to help anyone add tasteful, accessible, Motion‑powered animation to their UI while keeping sites fast and maintainable.
Not a library—an open component distribution
Like shadcn/ui, Sora UI is not a typical install‑from‑NPM library. It’s a component collection you can copy, modify, and customize directly in your codebase. This copy-first approach gives you maximum flexibility without wrapper overhead or styling workarounds.
What’s included
- Motion: Motion- and GSAP-powered building blocks you install with the shadcn CLI (
@soralabs/*) — buttons, text effects, disclosure, cursors, and more. Browse the Motion section for live previews, API reference, and install commands. - UI: Styled app components built with Base UI, Radix UI, and Motion — buttons, checkboxes, dialogs, and everyday UI. See the UI section.
- Blocks: Curated compositions and layout showcases built from primitives — see the Blocks for full-page examples and patterns you can adapt in your app.
- AI & MCP: Built-in Model Context Protocol (MCP) support via
@soralabs/xmcp, providing AI assistants with live tools, component schemas, and architectural composition rules.
Motion-first, powered by Motion and GSAP
While Motion serves as the primary engine for reactive micro-interactions, layout transitions, and spring physics, Sora UI also utilizes GSAP (and ScrollTrigger) whenever needed.
For complex timeline orchestrations, scrub-driven scroll animations, horizontal track pinning, and high-performance inertia flings, GSAP provides rock-solid precision. We choose the best tool for each specific interaction without locking you into a single paradigm.
Understood by Humans & AI
Sora UI provides UI components whose behavior, accessibility constraints, motion semantics, and composition rules are understandable by both humans and AI.
- First-class MCP Server: With our remote MCP server (
apps/xmcp), AI coding assistants (such as Claude Code, Cursor, Windsurf, and v0) can search documentation, inspect installable primitives, fetch source code, and validate component compositions against accessibility constraints. - Agent Metadata: Registry components publish structured
agentMetadata(intent, accessibility constraints, motion physics, and composition rules) so models reason accurately rather than guessing. - Continuous AI Focus: We continuously enhance agent tooling, context delivery, and automation to provide a reliable UI engineering experience for developers pair-programming with AI.
Inspiration & attribution
Most primitives and components here take inspiration from patterns already common on the web — sometimes adapted directly, then reworked, restyled, or extended. We don't claim every idea originated with us, and given how much prior art exists in this space, something may resemble work you've seen elsewhere.
If you recognize a component that's too close to your own work, missing credit it deserves, or you just have a concern about a specific primitive, reach out and we'll sort it out.
Community
Questions, bugs, and ideas are welcome on our GitHub community hub — open an issue or join Discussions.
Why Sora UI?
- Copy‑first: Install components into your project and adapt them at their core to your design system.
- Animation‑first (Motion + GSAP): Consistent, composable motion patterns powered by Motion, with GSAP stepping in seamlessly for advanced scroll & timeline interactions.
- Understood by Humans & AI: Native MCP tools and structured agent metadata so both developers and AI pair programmers reason accurately about component behavior and composition.
- Performance & accessibility: Sensible defaults and reduced-motion support that keep your site fast by default.
- Style‑agnostic: Not prescriptive about look and feel; baseline styles are minimal and easy to restyle with Tailwind CSS.
- Multi‑primitive support: Components built across multiple headless foundations (Radix UI, Base UI).
- Complementary to Magic UI and shadcn/ui: Works alongside these projects, filling the animation‑focused gap.
Built by Axyl. A motion-first component registry for React.
Last updated: 9/15/2026