// the find
codewithMUHILAN/Lightswind-UI-Library
The AI-native CLI-first React component library. 160+ animated, accessible, production-ready components with MCP Server support for Cursor, Claude & GitHub Copilot. Copy-paste architecture — you own the code.
A shadcn/ui-style component library for React: the CLI copies raw .tsx source into your project instead of installing a runtime package, and it ships 160+ components ranging from basic UI primitives to 3D/WebGL and GSAP/Framer Motion animated widgets. Aimed at developers who want shadcn's ownership model but with a much bigger, flashier component catalog, plus an MCP server so AI coding agents can browse and install components directly.
The dependency resolution in the CLI is real, not just marketing — adding `toast` pulls in `progress` automatically via `bin/component-deps.json`, which is the actual hard part of a copy-paste registry (shadcn's own CLI has had rough edges here). The MCP server exposes genuinely useful tools (`search_components`, `get_component`, `get_usage_example`) rather than just a wrapper around the docs site, so an agent can install a component without scraping the README. Component breadth is unusually wide for this category — 3D/WebGL pieces, shader backgrounds, and cursor effects aren't things you'll find in shadcn or Radix, and each one is a standalone `.tsx` + `.json` pair in the registry rather than a monolithic bundle.
`lib/verifyUser.ts` and `lib/sso.js` sitting in the public repo for license-key verification is an odd choice for a library whose entire pitch is 'you own the code' — Pro components are gated behind `sk_pro_` keys checked against a remote service, so a chunk of the catalog isn't actually yours to copy. There's no test directory anywhere in the tree, and the only CI workflow is `release.yml` — with 150+ component files, nothing appears to catch a broken `.tsx` before it ships. `lib/githubClient.ts` suggests the CLI fetches component source from GitHub at install time rather than bundling it in the npm package, meaning `npx lightswind add X` depends on GitHub being reachable and the registry path not changing — a silent breaking point for CI pipelines or offline installs. The README's own comparison table undercuts its headline claim: it says Lightswind is 'the only component library in the world' with an MCP server while the same table marks MCP support as supported for shadcn/ui, Radix UI, and Material UI too.