Skip to main content
Glama

WunderUI MCP

An MCP server that gives an AI coding agent the WunderUI design system: design tokens, the component inventory with real prop signatures, page templates and starter snippets. The agent builds with the library instead of reinventing a data grid out of raw divs.

claude mcp add wunderui -- npx -y wunderui-mcp

Works with Claude Code, Cursor, Windsurf, Cline, Codex, VS Code and any other client that speaks MCP over stdio. No key and no account needed.

Tools

Tool

What the agent gets

list_components

The inventory, filterable by category, plan (free or pro) or free text

get_component

Exports, the TypeScript prop signature, the import line, an example, the docs URL

get_tokens

Light and dark tokens as JSON, a CSS block, or Tailwind @theme mappings

get_design_md

The full DESIGN.md, or one section (rules, donts, tasks, tokens, inventory, reference, templates, starters)

list_templates

The full-page templates and what each is built from

get_starter

Copy-paste TSX: app shell, dashboard, data grid, AI chat, theming

get_library_info

Package name, version, install commands, stack, counts, data source

get_instructions

The short, always-on rules (components, tokens, motion, copy) for CLAUDE.md / AGENTS.md

list_skills

The WunderUI agent skills, free and Pro

get_skill

One skill's instructions (SKILL.md), so the agent can follow it without installing — Pro skills need WUNDERUI_LICENSE_KEY

get_block_source

The React source of a UI block and its shared helpers — needs a Pro key in WUNDERUI_LICENSE_KEY

Every component carries its plan. On the Free plan, an agent should only use components marked free; the others need WunderUI Core or Pro.

Related MCP server: open-design-system-mcp-starter

Resources

Clients that support MCP resources can attach the design context without a tool call. Read-only, and the same data as the tools above:

Resource URI

What it holds

wunderui://design-md

The full DESIGN.md (markdown)

wunderui://design-json

The machine-readable design data (tokens, inventory, templates, skills)

wunderui://tokens

Light and dark token values

wunderui://instructions

The short rules for CLAUDE.md / AGENTS.md

wunderui://components

The component inventory: name, category, plan, description

wunderui://components/{slug}

One component in full (one resource per component, listed by the server)

The tools stay for clients without resource support.

Install

Claude Code

claude mcp add wunderui -- npx -y wunderui-mcp

Cursor: .cursor/mcp.json

{
  "mcpServers": {
    "wunderui": { "command": "npx", "args": ["-y", "wunderui-mcp"] }
  }
}

Windsurf, Cline, Codex, VS Code: the same shape, in that editor's MCP config.

Installing WunderUI itself

The server describes the library; it does not ship it. @wunderui/react on npm is WunderUI Free (the free components only). Core and Pro licence holders install the full library from the wunderui-core download (the wunderui-setup agent skill does it for you), and the server tells agents exactly that.

Where the data comes from

data/design.json and data/DESIGN.md are generated from the WunderUI source with every release: tokens from the stylesheet, props from the built type definitions, names and descriptions from the docs.

The server starts with the bundled copy and answers immediately. In the background it fetches the current design.json and DESIGN.md from wunderui.com and switches to them when they are at least as new, so agents see new components without a package update. get_library_info reports which source is in use.

Variable

Effect

WUNDERUI_OFFLINE=1

never touch the network, use the bundled copy

WUNDERUI_SITE=<url>

fetch the live data from another origin

WUNDERUI_LICENSE_KEY=<key>

your WunderUI Pro key — unlocks Pro skills (get_skill) and block source (get_block_source); sent only to wunderui.com

Without MCP

The same data is served as static files for agents and editors that don't speak MCP:

  • https://wunderui.com/DESIGN.md: paste at the top of a prompt

  • https://wunderui.com/llms.txt: the llms.txt convention

  • https://wunderui.com/design.json: the same structured index

Verify

npm install
npm run smoke

Starts the server with a real MCP client and calls every tool once.

Releasing

  1. Bump the version in package.json and in server.json (top-level version and packages[0].version — the workflow refuses to publish when they differ).

  2. Commit, tag vX.Y.Z and push the tag. The Publish to npm workflow publishes to npm (Trusted Publishing) and then publishes server.json to the MCP Registry with GitHub OIDC — no tokens.

  3. If the registry ever falls behind npm, run the workflow by hand (Actions → Publish to npm → Run workflow) with registry_only ticked; it publishes the current server.json for a version that already exists on npm.

Licence

The server code is MIT. The WunderUI components it describes are licensed per plan, see wunderui.com/pricing.

Available Tools

11 tools
get_block_sourceGet a WunderUI block's source (Pro)A

The React source of a UI block (e.g. category 'app', block 'billing'), optionally one screen, plus the shared helpers it imports. Needs a WunderUI Pro key in WUNDERUI_LICENSE_KEY. Use https://wunderui.com/api/registry/index to see every block.

Inputs: block (required), category (required), screen.

get_componentGet a WunderUI componentA

Everything needed to use one component correctly: its exported names, the TypeScript prop signature straight from the build, a props table per export (type, allowed values, default, required, description), its anatomy (parts and data-slot names), best practices, the CSS variables it reads with their defaults, the import line and a link to its documentation page. Also answers for hooks (signature, parameters, return value, notes), providers and utilities (useToast, ThemeProvider …).

Inputs: name (required).

get_design_mdGet the WunderUI DESIGN.mdA

The complete design context as one markdown document: install steps, the rules an agent should follow, every token, the component inventory with props, and starter snippets. Pull this once at the start of a build.

Inputs: section.

get_instructionsGet the short WunderUI rulesA

The short, always-on rules for building with WunderUI (components, tokens, motion, copy) — the text to keep in CLAUDE.md / AGENTS.md. Read this first; use get_design_md for the full context.

Inputs: no named parameters.

get_library_infoGet WunderUI package infoB

Package name and version, install commands, the stack it is built on, and how many components, categories and templates exist.

Inputs: no named parameters.

get_skillGet a WunderUI agent skillA

Returns one skill's instructions (its SKILL.md) from wunderui.com, so the agent can follow the workflow without installing the skill. Pro skills are sent only with a valid Pro key in WUNDERUI_LICENSE_KEY. Scripts the skill mentions come with the installed skill (wunderui.com/skills).

Inputs: name (required).

get_starterGet a WunderUI starter snippetA

Copy-paste TSX for a common composition, wired with the correct props: an application shell, a dashboard row, a data grid, an AI chat, or the theming pattern.

Inputs: kind (required).

get_tokensGet WunderUI design tokensA

The design tokens for light and dark, in the format you need. Use these instead of hardcoding colours; overriding them is how WunderUI is themed.

Inputs: theme, format.

list_componentsList WunderUI componentsA

The WunderUI component inventory: name, category, plan (free or pro) and one-line description. Filter by category, plan or a free-text query. Call this first to find out whether a component already exists before building one by hand. On the Free plan use only components with plan "free".

Inputs: plan, query, category.

list_skillsList WunderUI agent skillsA

The agent skills that build and check with WunderUI (set up a project, build screens, theme from a brand colour, migrate from shadcn/MUI/Chakra, token check, motion and accessibility audits, Figma). Free skills work for everyone; Pro skills need WUNDERUI_LICENSE_KEY.

Inputs: no named parameters.

list_templatesList WunderUI page templatesA

Full pages assembled only from WunderUI components — a dashboard, a settings page, an AI inbox and a sign-in screen. Start from one of these instead of an empty file.

Inputs: no named parameters.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation3/5

    Most tools are clear, but three code-example tools overlap heavily: list_templates (full pages), get_starter (compositions), and get_block_source (Pro block source) all answer a vague 'show me an example' request. get_design_md also duplicates the content of get_tokens, get_instructions and list_components, which the description acknowledges but still creates a routing decision for the agent.

    Naming Consistency5/5

    Every tool follows a strict list_/get_ prefix with a snake_case noun object (list_components, get_component, get_tokens, get_skill, get_block_source). The pattern is predictable and the singular/plural distinction cleanly separates listing from fetching a single item.

    Tool Count5/5

    11 tools is well within the ideal 3-15 range for a design-system server. Each tool maps to a distinct artifact type (components, tokens, templates, starters, skills, blocks, library meta) and none feel redundant or padded at the count level.

    Completeness4/5

    The surface covers the full read-only lifecycle an agent needs: discovery (list_components), detail (get_component), theming (get_tokens), guidance (get_instructions/get_design_md), code scaffolds (templates/starters), and skills/blocks. Minor gap: there is no tool to retrieve a single component's raw source (only Pro block source), so an agent may still have to write component internals by hand.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to query a workspace's design system before writing UI and validate generated code against the same system afterward, using configurable token and component sources.
      13 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      It lets AI coding agents look up design tokens, component specifications, and prohibition rules on demand, then validate generated HTML or JSX with the same lint logic used by CI and editor hooks so violations are caught and corrected immediately. It also exposes the design constitution and rule sets as resources for reference during generation.
      6
      206 npm
      202
      MIT