shadcn/ui registry directory vs Shoogle (2026)

shadcn/ui registry directory vs Shoogle

2 compared on 6 criteria

On what you get without paying, shadcn/ui registry directory is All of it and Shoogle is Everything on the site. On cheapest paid option, shadcn/ui registry directory does not publish it and Shoogle does not publish it. On what it publishes, shadcn/ui registry directory does not publish it and Shoogle is 292 registries; item count not published. On how you install from it, shadcn/ui registry directory is npx shadcn add @<registry>/<component> and Shoogle is Through the official shadcn CLI, as a namespace. On how something gets listed, shadcn/ui registry directory is A documented add-a-registry route and Shoogle is Pulled from shadcn's own directory, plus submissions. On what it says about the code's quality, shadcn/ui registry directory is Explicitly not reviewed, and it says so and Shoogle does not publish it. BlockDex publishes this table and is one of the things in it, so read the case for the other side below rather than taking the table's word for it. Every figure was read off the named company's own page on or since 2026-09-06; the URLs and the dates are at the foot of this page, and a job re-fetches each one on a schedule and fails when a figure is no longer on the page it came from.

compared2criteria6sources read3verified2026-09-06

Criterionshadcn/ui registry directoryShoogleWhat you get without payingAll of it"Discover community registries for shadcn/ui components and blocks. These registries are built into the CLI with no additional configuration required." No account and no key; what each listed registry charges is its own business.Everything on the siteThere is no pricing page — https://shoogle.dev/pricing returned 404 when this row was checked — and no account gate on browsing, the directory or the MCP endpoint. The only commercial surface anywhere in the navigation is Sponsor, which is the same model SkillWorks runs and the opposite of a per-seat catalogue.Cheapest paid optionNot publishedThe registry directory and the registry documentation publish no price, plan or tier of any kind. Read on ui.shadcn.com's own directory page on 14 August 2026.Not publishedNo plans, no tiers and no purchase surface. /pricing 404s and the MCP page's only call to action is the Discord. Read as sponsor-funded rather than free-forever: the site publishes no commitment either way, so this is what the page carries rather than what a visitor can infer.What it publishesNot publishedThe directory lists community registries but publishes no total for how many it carries and no per-registry item count. Read on ui.shadcn.com's own directory page on 14 August 2026 — which is the specific gap BlockDex crawls to fill.292 registries; item count not published"S 292 registries" on the directory, over the same community set shadcn's own directory lists. The MCP page carries a UI-components counter and a registries counter, but both render as animated digit rollers rather than a number, so the page states no item total. The registry endpoint is bounded rather than complete in another way too: https://shoogle.dev/r/registry.json?q=button answers with pagination {"hasMore":false,"limit":100,"total":100} — a top-100 per query, not a corpus size.How you install from itnpx shadcn add @<registry>/<component>The canonical command, and the reason the other three all reference this CLI rather than shipping their own. The docs add that "the registry works with any project type and any framework, and is not limited to React".Through the official shadcn CLI, as a namespace"Search with npx shadcn@latest search @shoogle — filter by type, limit, and offset without leaving your terminal." It is a shadcn registry namespace, so results come back already addressed to their SOURCE registry — the button row of that endpoint carries "addCommandArgument": "@animate-ui/primitives-buttons-button" — and the install runs against the origin registry rather than through Shoogle. The same index is also served as an MCP server over streamable HTTP for Claude, Cursor, Windsurf, VS Code and Cline. No other entry in this table is reachable from inside the CLI.How something gets listedA documented add-a-registry route"Don't see a registry? Learn how to add it here", with "Add a registry — learn how to add a registry to the directory" as its own documentation page beside Getting started, Authentication and Namespaces.Pulled from shadcn's own directory, plus submissions"Community registries pulled from the shadcn/ui directory, with sorting to make it easier to track newly added registries." So the inclusion decision is shadcn's, not Shoogle's, with a documented route for a registry that is not in it yet. Categories are assigned per registry — Design System, Marketing UI, AI Blocks and twenty more — and the sort is by when the registry was added.What it says about the code's qualityExplicitly not reviewed, and it says so"Community registries are maintained by third-party developers. Always review code on installation to ensure it meets your security and quality standards." The only one of the four that states the limit of its own vouching rather than implying there is none.Not publishedNothing on the directory or the MCP page claims review, curation, testing or any check of the code behind a listing. The one quality statement the site makes is about itself: every page carries an Alpha badge beside the wordmark.

BlockDex publishes this table and is not one of the 2 compared. "Not published" means that company does not state the figure on the page cited below. It is not a claim that no such figure exists: this table prints what was read, not what was inferred.

shadcn/ui registry directory vs Shoogle — what you get without paying?

shadcn/ui registry directory: All of it. "Discover community registries for shadcn/ui components and blocks. These registries are built into the CLI with no additional configuration required." No account and no key; what each listed registry charges is its own business. Shoogle: Everything on the site. There is no pricing page — https://shoogle.dev/pricing returned 404 when this row was checked — and no account gate on browsing, the directory or the MCP endpoint. The only commercial surface anywhere in the navigation is Sponsor, which is the same model SkillWorks runs and the opposite of a per-seat catalogue. Read from ui.shadcn.com and shoogle.dev on 2026-09-06.

shadcn/ui registry directory vs Shoogle — cheapest paid option?

shadcn/ui registry directory does not state it on ui.shadcn.com. The registry directory and the registry documentation publish no price, plan or tier of any kind. Read on ui.shadcn.com's own directory page on 14 August 2026. Shoogle does not state it on shoogle.dev. No plans, no tiers and no purchase surface. /pricing 404s and the MCP page's only call to action is the Discord. Read as sponsor-funded rather than free-forever: the site publishes no commitment either way, so this is what the page carries rather than what a visitor can infer. Read from ui.shadcn.com and shoogle.dev on 2026-09-06.

shadcn/ui registry directory vs Shoogle — what it publishes?

shadcn/ui registry directory does not state it on ui.shadcn.com. The directory lists community registries but publishes no total for how many it carries and no per-registry item count. Read on ui.shadcn.com's own directory page on 14 August 2026 — which is the specific gap BlockDex crawls to fill. Shoogle: 292 registries; item count not published. "S 292 registries" on the directory, over the same community set shadcn's own directory lists. The MCP page carries a UI-components counter and a registries counter, but both render as animated digit rollers rather than a number, so the page states no item total. The registry endpoint is bounded rather than complete in another way too: https://shoogle.dev/r/registry.json?q=button answers with pagination {"hasMore":false,"limit":100,"total":100} — a top-100 per query, not a corpus size. Read from ui.shadcn.com and shoogle.dev on 2026-09-06.

When should I pick shadcn/ui registry directory, and when Shoogle?

shadcn/ui registry directory — You want the first-party answer and the shortest possible path from finding a component to having it in your repository. This is the mechanism every other entry here sits on top of, it costs nothing, and the registries in it are "built into the CLI with no additional configuration required" — so `npx shadcn add @<registry>/<component>` works with no account, no key and no config. It is also the only one of the four that tells you plainly what it does not do. Shoogle — You want the answer inside the tool you are already in rather than in a browser tab. Shoogle is the only one here that registers as a shadcn NAMESPACE, so `npx shadcn@latest search @shoogle` searches across community registries from the terminal and the install runs through the official CLI — no site, no copy-paste, and the same route works from any MCP client that speaks streamable HTTP. It is the shortest path from "is there a component for this" to the component being in the project. It also labels itself Alpha, and it publishes no figure for how many items that search covers.

When each of these is the right pick

BlockDex does not sell any of these and scores them. Each case below is the one that option wins.

shadcn/ui registry directory: You want the first-party answer and the shortest possible path from finding a component to having it in your repository. This is the mechanism every other entry here sits on top of, it costs nothing, and the registries in it are "built into the CLI with no additional configuration required" — so `npx shadcn add @<registry>/<component>` works with no account, no key and no config. It is also the only one of the four that tells you plainly what it does not do.
Shoogle: You want the answer inside the tool you are already in rather than in a browser tab. Shoogle is the only one here that registers as a shadcn NAMESPACE, so `npx shadcn@latest search @shoogle` searches across community registries from the terminal and the install runs through the official CLI — no site, no copy-paste, and the same route works from any MCP client that speaks streamable HTTP. It is the shortest path from "is there a component for this" to the component being in the project. It also labels itself Alpha, and it publishes no figure for how many items that search covers.

Other shadcn registries and block libraries compared head to head

What was checked, and when

Prices and limits move. Every source is printed here so a reader can check it on the day they read this, and a job re-fetches each of these URLs on a schedule and fails when a figure above no longer appears on the page it came from.

shadcn/ui registry directory, ui.shadcn.com/directory: What you get without paying, Cheapest paid option, What it publishes, How you install from it, How something gets listed, What it says about the code's quality. Read 2026-09-06.
Shoogle, shoogle.dev/mcp: What you get without paying, Cheapest paid option, How you install from it. Read 2026-09-06.
Shoogle, shoogle.dev/directory: What it publishes, How something gets listed, What it says about the code's quality. Read 2026-09-06.

Every cell above was confirmed against its own source on or since 2026-09-06. /compare/shadcn-registry-vs-shoogle