Find React components in the encode-ui registry by name, alias, or keyword. Web engine: a plain substring filter over the index fetched from the deployed registry (name, aliases, curated keywords, title, description) — exact names and aliases ("modal", "toast") work best; loose behaviour phrasing may miss. Terms split on punctuation and single characters are dropped, so "toast?" and "a dialog." behave like the bare words. For discovery and planning, read the catalog resource encode-ui://catalog (≈20k tokens) once and judge the descriptions yourself. Every hit carries the exact install command. score is rank-derived (scoreKind "lexical"), comparable only within one result set, and cosine is always null — no score here is calibrated. A filter cannot prove absence: for "find ALL X" or "does the registry have X?" use list_groups + list_components and judge the descriptions yourself.

Components related to a given one — same group, shared categories, and composition edges, computed from the fetched registry index. Useful for "what else is like this" and for finding variants. score is a structural heuristic (scoreKind "lexical"), comparable only within one result set; these are not embedding-space neighbours.

Metadata for one component by name: description, group, dependencies, provenance/license, and the install command. Reports the byte size of the source and demo without sending them — fetch those from get_component_source once you know what they cost.

Every TSX file one component ships, or its demo usage example, in fenced code blocks. A multi-file component returns ALL of its files — the public module plus every sibling it imports (.parts.tsx pairs, block modules) — because the entry file alone does not compile. Check sourceBytes/demoBytes on get_component first if size matters. Returns code as text rather than a JSON field, so it stays readable.

The registry taxonomy with a component count per group. Use a slug from here as the group filter on search_components, or enumerate a group in full with list_components.

Every component in one group — full membership, not a ranked sample. Search always returns its top k, so "list ALL X" and "does the registry have X?" need this instead: enumerate, then judge the descriptions yourself. Returns name, title, and description per item; get_component has the details.

One npx shadcn@latest add command installing all the named components at once. Duplicates collapse; names with no such component come back under unknown.

Verified lucide-react icon names — never guess an icon import. Two modes (at least one of query/names/category is required): query searches names, curated tags, and categories by what the icon should depict ("shopping cart", "danger warning"); names verifies exact spellings and resolves legacy aliases (Home → House, with the deprecation flagged). category filters or browses. Hits carry the canonical name, the import identifier, and tag/category context; the registry itself ships no icon components — lucide-react 0.511.0 is the icon layer, auto-installed with any icon-using item.