labsUI
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
labsUI
labsUI components live in this project as source: edit them like your own code.
The copy here is the version that installed it (labsui.json), often older
than this labsUI. Asked how an installed component behaves, or to change one,
run labsui diff <name> (or the MCP diff tool) first, before you
answer: say what the current version changes, and when it already does what
is asked, offer labsui update <name> instead of editing by hand.
Before writing UI
Look a component up before using it:
labsui view <name>(or the MCPviewtool) gives exact props, an example and what it installs. Do not guess props.Find one by intent:
labsui search date range. Add it withlabsui add <name>; it brings everything it imports.For a whole page or app (blog, docs, shop),
labsui searchalso finds recipes:labsui view <recipe>lists the components a checked build used and the patterns it needed.After changing the setup, run
labsui doctor.
Look and layout
Before the first page, pick a direction from the product: who it is for and how it should feel. Set it once with tokens, not per element: an accent preset (
setAccent()from@/lib/theme, ordata-accenton<html>),--radiusin your CSS (0 for sharp, larger for soft), a display font fromnext/fontfor headings, light or dark first.Lead with the product's own content (items, prices, data, a working demo) and give one thing the most weight. Avoid the template look: a small label above every heading, a centered hero with two equal buttons, rows of three identical cards, round numbers like 10,000+.
Writing code
Import primitives from
@/components/ui/<file>, blocks from@/components/blocks/<file>.Compose primitives; use a variant or prop before restyling. Merge classes with
cn()from@/lib/utils; components takeclassName.Motion:
motion/reactwithspringfrom@/lib/utils, no duration tweens. Animatex,y,scale, not atransformstring.Colors are tokens:
background,foreground,card,popover,primary,secondary,muted,accent,destructive,success,warning,border,input,ring(each with-foreground). Text inprimaryor a status color on a surface uses the-inktwin (text-primary-ink,text-destructive-ink), nevertext-primary.No gradients or glows. Radii
rounded-lg|xl|2xl, shadowsshadow-xs|sm|md.Focus ring:
outline-none focus-visible:ring-[3px] focus-visible:ring-ring/50.Dark mode is
.darkon<html>; switch it withsetTheme()from@/lib/theme.Feedback:
toast()from@/components/ui/toast,await confirm()from@/components/ui/confirm.<Toaster />and<Confirmer />are mounted once in the root layout.Server components pass only serializable props to client components: icons as elements (
icon={<Mail />}).Links in components render
<a>until the app sets its router's link once: wrap the root layout's body in<LinkProvider component={Link}>(@/lib/link,Linkfromnext/link). Then nav, footer, pager, sidebar and card links route on the client; noonNavigateneeded.Pointer targets are at least 24×24 px. Prefer native validation (
required,type,pattern).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Find labsUI components, blocks, hooks and helpers by name, export (useModal) or intent (date range, toast promise), and recipes for a whole app (blog, shop): a prompt checked on a fresh app with the items it used. All words must match, best match first; no query lists everything. Returns one line per hit: name, kind and summary, and says how many a limit left out. Start here when you don't know an item's name, then call view on the hits. |
| viewA | Read the docs of labsUI items by name: exact props and types, a usage line, full examples, and the items and npm packages each brings along; for a recipe, its prompt, the items it uses and the patterns the result needs. Call it before writing code with a component instead of guessing props; find names with search, install with add. |
| addA | Install labsUI items into the project: copies each item and everything it imports, then installs their npm packages. Existing files are kept, never overwritten. Returns the files written, the packages installed, dependencies kept that differ from this version (call update on them) and anything to mount once in the root layout. Needs init first; dryRun previews. To bring installed items to a newer version, use update instead. |
| initA | Set up labsUI in a project, once, before add: writes the styles, theme, utils and motion provider, imports labsui.css into the Tailwind stylesheet and records settings in labsui.json. Returns warnings, the files written and the root layout code to add. Needs React 19 and Tailwind v4; run doctor first if unsure. Safe to repeat: existing files are kept. dryRun previews. |
| diffA | Compare installed labsUI items with this labsUI version. Returns a unified patch per changed file, from the registry file to the project file (+ lines exist only in the project), with formatting: true when only blank lines or indentation differ and changedBy saying whose change it is since the installed version: upstream (only labsUI changed it; update replaces the file), local (only you did; update keeps it) or both (update merges), unset when that version can't be fetched; matching items are left out, a named item that isn't installed comes back with installed: false, and when nothing differs it says so. Use it before update to see what it will do. Needs init. |
| updateA | Bring installed labsUI items to this labsUI version. Unedited files are replaced; edited ones are merged three ways from the version that installed them, with conflict markers where both sides changed the same lines. Returns each changed item as replaced, merged, conflicts (with the files to resolve) or kept with the reason. Run diff first to see local edits; dryRun previews. Only for installed items: new ones go through add. |
| doctorA | Check the labsUI setup: React 19, Tailwind v4, the path alias, the stylesheet import, MotionProvider and themeScript wiring, mounted Toaster/Confirmer, missing npm packages or files, and local edits. Returns pass, warn or fail per check, each problem with its fix. Run it after init or add, or when components look unstyled; for line-level changes use diff. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| blog | A blog with a post list, long posts with highlighted code and a list of sections, and an about page. |
| docs-site | Docs with side navigation, code samples, a list of sections per page, previous and next links and a table of a function's options. |
| shop | A shop in euros with a product grid, a product page with photos and sizes, a cart and a checkout with shipping and payment options. |
| game-shop | A game server's store in euros: ranks for 30 days, 90 days or forever, cosmetics by category, the nickname that receives the order, payment options, server status, a community goal and top buyers. |
| laptop-comparison | Four laptops compared feature by feature in groups, with pickers on a phone and a switch that shows only the differences. |
| portfolio | A portfolio with an intro, a grid of projects, a page per project and a contact form. |
| admin-panel | A store admin in euros: a sidebar, orders with search, a status filter and row selection, a drawer that edits one order, a confirmation before deleting and a message after each change. |
| analytics | A store dashboard in euros: key figures that count up with their change, revenue over time, a date range with day, week and month, and a table of top products. |
| saas-landing | A landing page for a software product in euros: hero, features, customer quotes, plans with monthly and yearly billing, an FAQ, a newsletter and a footer. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool owns a distinct lifecycle step: init sets up, add installs new items, update upgrades installed ones, search finds names, view reads docs, diff compares, doctor checks health. The descriptions explicitly cross-reference each other (e.g. add says 'to bring installed items to a newer version, use update instead'), resolving the only potential overlaps between add/update and diff/doctor.
All seven tools are single lowercase words with no mixed casing or verb/noun style drift, matching a conventional CLI subcommand grammar. The lone noun ('doctor') is a standard CLI idiom and reads consistently with the rest.
Seven tools is well-scoped for a component-registry CLI, with no redundant or filler entries. Each tool corresponds to a genuine workflow stage an agent would need.
The surface covers setup, discovery, inspection, installation, upgrade, diffing and diagnostics, which is close to full lifecycle coverage. The notable gap is removal: there is no uninstall/remove tool for taking items back out, and no dedicated way to enumerate only installed items, though diff partially surfaces them.