Back to all days

Day 23 — UI/UX Design

Design System Component Library

Your Figma file says “primary-500.” Your CSS says “#6366F1.” Your Storybook says “indigo.” Nobody agrees.

An MCP server that manages the full design system — tokens, components, variants, dark mode values, accessibility scores, and dependency graphs. One source of truth instead of three that disagree.

Example Queries

“Show me all the color tokens with their dark mode values”
“Which components have an accessibility score below 90?”
“Give me the full breakdown of the Button component — every variant and a11y check”
“Run an accessibility audit and show me only the failing checks”
“What changed in the design system this week?”
“How healthy is the overall design system? Give me the big picture.”

Tools

6 MCP Tools

ToolWhat It Does
list_tokensList and search design tokens across 5 categories — colors, spacing, typography, shadows, and radii. Shows light and dark mode values with CSS variables.
list_componentsList all components with variant counts, accessibility scores, status, and category. Filter by owner, status, or component type.
get_componentDeep dive into a single component — every variant with props, all accessibility checks, token dependencies, and recent changelog.
a11y_auditRun an accessibility audit across all components or a specific one. Shows pass/fail checks, system score, and a prioritized fix list.
get_changelogBrowse the design system changelog — additions, updates, and fixes. Filter by component, author, or action type.
system_overviewHigh-level health check of the entire system — token coverage, component maturity, dark mode completeness, dependency graph, and team activity.

Component Library

12 Components

Button

actions

stable
8 variantsa11y: 98

Input

forms

stable
5 variantsa11y: 95

Modal

overlays

stable
4 variantsa11y: 92

Card

layout

stable
4 variantsa11y: 90

Badge

data-display

stable
5 variantsa11y: 96

Toast

feedback

stable
4 variantsa11y: 88

Avatar

data-display

stable
3 variantsa11y: 94

Tooltip

overlays

stable
3 variantsa11y: 91

Tabs

navigation

beta
3 variantsa11y: 85

DataTable

data-display

beta
3 variantsa11y: 78

Select

forms

draft
3 variantsa11y: 72

Skeleton

feedback

draft
3 variantsa11y: 100

Why This Build

Why a Design System Library?

Design systems are supposed to be the single source of truth. In practice, they're three sources of partial truth — a Figma file that's sort of up to date, a Storybook that's definitely behind, and a CSS file that nobody trusts.

The designer says “use the primary button.” The developer asks “which primary button? There are four.” The QA engineer files a bug because the border radius is 6px on one screen and 8px on another. Nobody wins.

This server manages 47 design tokens across 5 categories, 12 components with 48 variants, 26 accessibility checks, and a full dependency graph. Dark mode values are tracked at the token level. Every component has an accessibility score. Ask “which components need attention?” and get a prioritized list instead of a Slack thread.

Demo Data

What's Inside

47

Tokens

12

Components

48

Variants

26

A11y Checks

24

Dependencies

16

Changelog

Tokens span colors (primary, neutral, semantic), spacing (4px to 64px), typography (Inter + JetBrains Mono), shadows, and radii — all with CSS variable mappings and Figma references. Dark mode values are defined at the token level, not per-component. Components range from stable (Button, Input) to beta (DataTable, Tabs) to draft (Select, Skeleton). Accessibility checks include keyboard navigation, ARIA attributes, focus management, contrast ratios, and screen reader support.

Setup

Try It Locally

cd day23-design-system
npm install && npm run seed && npm run build

Then add the config to Claude Desktop and restart.

Your design system needs a conversation layer?

If your tokens live in Figma, your components live in Storybook, and your accessibility audit lives in a spreadsheet — let's put them all in one place.