21st.dev review

21st.dev is a hosted catalog and workflow for discovering UI source, not a runtime component API or a server you deploy. Its library contains components from multiple authors, along with prompts, templates, themes, icons and shaders. The core use case is to find a design, then move its source or instructions into an existing project.

In a typical stack, the catalog sits outside the application. A developer browses the site, copies a prompt into an AI coding agent, or uses the CLI, MCP or a shadcn command to install component source. The resulting code lives in the project repository and can be edited with the rest of the UI. The homepage describes components as React and TypeScript with Tailwind CSS, following shadcn conventions, and says they run anywhere React runs, including Next.js, Vite, Remix and Astro. That makes 21st.dev a design and code-discovery layer for React teams, rather than a dependency that must serve every production page.

The homepage describes an integration surface built around a hosted library, prompts, MCP and a terminal CLI—not a general REST API or application SDK. It names React, TypeScript and Tailwind CSS for component code, and says components use the shadcn registry format. The site also gives a shadcn CLI command for each component and shows a terminal example: npx 21st add hero hero.tsx.

For agent workflows, the site says to copy a prompt into Claude Code, Cursor, Codex or Lovable. It also advertises access through supported MCP clients, but does not name a protocol version or client compatibility matrix in the homepage text. No SDK languages beyond the component stack are named. Confirm SDK support, MCP setup, CLI options and required versions in the vendor's documentation before standardizing the workflow. There is no API authentication model, endpoint reference or webhook integration described on the homepage, so teams looking for those surfaces should confirm availability with the vendor.

The free plan costs $0, requires no card, and includes library search, two component copies or install commands a day, and five Design Bug Bot reviews. That daily copy limit is the point where regular use can require an upgrade. Builder costs $8 per month, or $6 per month billed yearly, for unlimited copies and installs, MCP and CLI access, and additional design assets.

Builder + AI costs $20 monthly or $15 per month billed yearly. It includes Builder features and 500, 1,000 or 2,000 AI credits a month; the selected credit amount affects the plan. Team costs $10 per user monthly or $7.50 per user billed yearly for 2–50 seats. Team + AI is listed at $18.75 per user per month billed yearly, with monthly pricing not listed. AI credit packs cost $5 per 100 credits and roll over month to month; automatic top-up is available with a customer-set monthly cap. The pricing page does not list request-based charges or compute fees. Model credit use and team seat count are the main bill variables.

The homepage says component source lands in your repository and is yours to edit. That lowers lock-in at the application-code level: installed components can be maintained as project files rather than served from 21st.dev at runtime. The vendor does not identify an open-source license for the catalog or its service in the stated materials, so check the license attached to each component before redistributing or using it commercially.

21st.dev is presented as a hosted catalog, not a self-hosted server or package you can run in your own infrastructure. The vendor does not describe a data-export process for bookmarks, collections or other account data. If you leave, your installed source remains in your repo, but saved library organization and access to the hosted catalog may not. Ask the vendor about account-data export and component licensing if those affect a production workflow.

The main production advantage is that the delivered component source is editable in your repository. That keeps the rendered UI under your application's build and deployment path, rather than adding a hosted runtime dependency. The main operational limit is on the service side: free users get two copies or install commands a day, while paid Builder plans remove that cap. AI plans meter generation and Design Bug Bot work through credits.

The vendor does not publish API request limits, uptime commitments or security and compliance details in the stated materials. Confirm those points, along with component licensing and MCP client support, before making the catalog a team dependency. Reddit sentiment reflects the free-tier change: one r/vibecoding thread complains that the allowance fell to two daily copies, while replies argue that creators should be paid. A separate r/webdev discussion values 21st.dev as a source of varied, copyable components. Treat those comments as individual reports, not reliability data.