Categories › Software Development › Frontend, UI components & design-to-code
React + Tailwind UI components and recipes your AI coding tool can search and install.
Remote server: your requests and data go to liro.dev. Claude Code: claude mcp add --transport http liro https://liro.dev/api/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
search_components — Find Liro React + Tailwind components by what they do. Returns the best matches first with slug, category, access (free or pro) and version.get_component — Everything about one component except its source: when to use it, props, variants, npm dependencies, the files it installs, a typechecked usget_component_code — The complete source for one component and every file it imports, ready to save at the paths given. Free components need a free Liro account'get_installation — Installation for one or more components: the one-time @liro registry setup for components.json, the shadcn CLI command (always @liro/<slug>,list_categories — The categories in the Liro catalogue with the components in each, plus the library contract: stack, theme, access, install path, and the accsearch_templates — Find complete Liro React / Next.js templates: what each is, its stack, a live preview and how it is licensed.get_template — One template's details and whether the caller may download it. Never returns the template's files.check_access — Whether the caller can take a component or template, and why: free, subscriber, lifetime, purchased or unauthorized.get_theme — The theme's colour tokens (light and dark values, and what each one colours), how to restyle Liro to a brand from your own CSS without editiget_recipe — Complete, runnable files that combine several Liro components the way they fit together: an AI chat app shell (Sidebar + Conversation HistorNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.