Skip to main content
Glama

labsUI

Clean, composable React components with one smooth spring for every motion. Hand-made, accessible, and copied into your project so you own the code.

Docs and live demos · npm · JSR · MCP registry · Glama

Chromium Firefox WebKit WCAG 2.2 AA MCP server score on Glama

Why labsUI

  • One spring. Every animation shares { type: "spring", stiffness: 400, damping: 30 }, so the whole UI moves the same way. Reduced motion is respected everywhere.

  • You own the code. npx @kznlabs/labsui add writes plain TSX into your repo. No runtime package to upgrade around, edit anything.

  • Accessible by default. WAI-ARIA patterns, full keyboard support, and WCAG AA contrast in light and dark mode for all eight accent colors.

  • Server-friendly. Many components are server-safe, and form controls use native validation, so forms work without JavaScript and with Server Actions.

  • 80+ components and blocks. Inputs, overlays, navigation, data display, charts, motion helpers, and ready-made blocks like pricing, site header and changelog.

Why labsUI has more, including when it is not a fit.

Related MCP server: Next.js DevTools MCP

Accessibility and browsers

CI runs an automated sweep on pull requests (the pages a change reaches) and daily (everything): all component pages, light and dark, at 390 px and 1280 px, in three browser engines. The badges show the latest full run on main.

Check

Required

WCAG 2.2 A + AA rules (axe)

0 violations

JavaScript errors

none

Sideways page overflow

none

Every control reachable by a click

pass

Scroll containers move under the wheel

pass

Menus, popovers, tabs, sliders, Escape, focus

pass

Pointer targets

24 × 24 px or larger

Text contrast, both themes

4.5:1 or higher

Engine

Covers

Status

Chromium

Chrome, Edge, Brave, Opera, Opera GX

Chromium

Gecko

Firefox

Firefox

WebKit

Safari (macOS); iOS shares the engine

WebKit

Minimum versions come from Tailwind CSS v4: Chrome 111, Safari 16.4, Firefox 128. Two features enhance where supported and fall back cleanly: styled select popups (appearance: base-select, Chromium and newer Safari; elsewhere the native list) and auto-growing textareas (field-sizing; a resize handle in Firefox).

Automated checks find many problems, not all: axe covers roughly half of the WCAG criteria, so this is not a full conformance audit. Not yet covered: screen reader passes, real phones (iOS Safari, Android Chrome), Samsung Internet and other less common browsers.

Quick start

Requires React 19, Tailwind CSS v4 and a @/* path alias in tsconfig.json. The CLI runs on Node.js 22 or newer, or Deno.

npx @kznlabs/labsui init               # styles, theme, utils, motion provider
npx @kznlabs/labsui add button dialog  # components plus everything they import
npx @kznlabs/labsui search date range  # find by name, export or intent
npx @kznlabs/labsui view dialog        # exact props, examples, what it installs
npx @kznlabs/labsui doctor             # check the setup, with a fix for each problem

Any package manager works: bunx, pnpm dlx, yarn dlx and deno run -A jsr:@kznlabs/labsui too, and npm packages install with whichever one your lockfile shows. Bun is recommended: labsUI is built with it. See the CLI reference for every option.

Coding agents get the same through npx @kznlabs/labsui mcp, an MCP server with search, view, add, init, diff, update and doctor tools plus the library's coding rules, or through --json on any command. It's listed in the MCP registry as io.github.kznlabs/labsui and on Glama:

{
	"mcpServers": {
		"labsui": { "command": "npx", "args": ["-y", "@kznlabs/labsui", "mcp"] }
	}
}

Agents that share no workspace, such as Claude Desktop, also need "--cwd", "/path/to/app" after "mcp" (setup).

import { Button } from "@/components/ui/button";

export function DeleteButton({ onDelete }: { onDelete: () => void }) {
	return (
		<Button variant="destructive" confirmLabel="Yes, delete" onClick={onDelete}>
			Delete
		</Button>
	);
}

What's inside

Group

Examples

Actions & inputs

Button, Field, Select, Combobox, Date picker, Slider, OTP, Tag input

Overlays & feedback

Dialog, Drawer, Popover, Dropdown and context menus, Command palette, Toast

Navigation

Tabs, Sidebar, Navigation menu, Breadcrumb, Pagination, Table of contents

Data display

Table, Data table, Chart, Carousel, Timeline, Code, Terminal

Layout

Card, Accordion, App window, Resizable panels, Scroll area

Motion

Reveal, Count to, Typewriter, Text swap, Custom cursor

Blocks

Pricing, Site header, Post card, Product card, Cart, Comparison table

Theming is built on OKLCH tokens with light and dark mode and eight accent presets, or your own hue through --accent-hue.

Development

labsUI is built with Bun, and the repo scripts run on it, so install Bun to work on the library itself.

bun install
bun dev                     # docs site with every component
bun run lint                # Biome
bun run typecheck           # also rebuilds the registry and API docs
bun run check-dead-code     # Knip
bun test                    # unit tests for helpers and the CLI
bunx markdownlint-cli2      # Markdown

The docs site deploys from main to GitHub Pages. A cli-v<version> tag publishes the CLI to npm and JSR.

License

MIT

Available Tools

7 tools
addAdd labsUI itemsA
Idempotent

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.

Inputs: names (required), dryRun.

diffDiff installed labsUI itemsA
Read-only

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.

Inputs: names.

doctorCheck the labsUI setupA
Read-only

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.

Inputs: no named parameters.

initSet up labsUIA
Idempotent

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.

Inputs: dryRun.

updateUpdate labsUI itemsA
DestructiveIdempotent

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.

Inputs: names, dryRun.

viewView labsUI itemsA
Read-only

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.

Inputs: names (required), source.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol server that fetches up-to-date, version-specific documentation and code examples from libraries directly into LLM prompts, helping developers get accurate answers without outdated or hallucinated information.
      2
      64,930
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides specialized development tools and utilities for Next.js, allowing AI agents to perform runtime diagnostics and access official documentation. It enables automated context initialization and real-time interaction with Next.js development servers to query application state.
      4
      170,540 npm
      838
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to inspect a project's design tokens and component catalog, audit React/Tailwind files against seven static UI quality rules, score overall UI health, and apply auto-fixes that are re-audited and reverted on regression. It works both locally over filesystem access and remotely on raw TSX/JSX or CSS snippets passed directly as strings.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to search across 340+ React UI registries, inspect component code and quality scores, compare options, detect a project's stack, and generate or execute safe transactional install plans. It provides read and write safeguards with dry-run planning and rollback.
      1
      MIT