WunderUI

io.github.Kl-webmedia由 GitHub 帳號 Kl-webmedia 發布v1.2.1更新於 Nov 3, 2026

The WunderUI design system for coding agents: components, props, tokens, rules and skills.

已驗證STDIO僅桌面知識與記憶開發者工具

概覽

AI 產生的概覽

為編碼助理提供 WunderUI React 設計系統:元件清單、真實 props 簽名、設計權杖、頁面範本、起始程式碼與技能。

可以做什麼
  • 依分類、方案或關鍵字篩選元件清單,並檢視單一元件的匯出、TypeScript props、結構與 CSS 變數
  • 以 JSON、CSS 或 Tailwind 主題對應形式讀取明暗兩套設計權杖,以及完整設計文件與簡短的常駐規則
  • 列出整頁範本,並取得應用外殼、儀表板、資料表格、AI 對話或主題化的可複製 TSX 起始程式碼
  • 列出代理技能並取得某個技能的說明,以及取得 UI 區塊的 React 原始碼與其共用輔助程式
適用情境
適合助理使用 WunderUI 建置 React 介面時,重用既有元件與權杖,而不是自行拼湊標記。也適用於從其他元件庫遷移,或希望不必貼上文件就能在編輯器中取得設計規則。
執行需求
以 stdio 在本機執行,通常透過 npx 啟動 wunderui-mcp 這個 npm 套件,因此需要 Node.js。免費內容不需帳號或金鑰。選用環境變數:WUNDERUI_LICENSE_KEY 用於 Pro 技能與區塊原始碼,WUNDERUI_OFFLINE 用於離線,WUNDERUI_SITE 用於更換資料來源。會連網從 wunderui.com 更新設計資料。
安裝前請注意
此伺服器只描述元件庫,並不安裝它;實際的 React 套件需另行安裝。Pro 技能與區塊原始碼需要在 WUNDERUI_LICENSE_KEY 中提供 WunderUI Pro 金鑰,該金鑰會傳送至 wunderui.com。預設情況下伺服器會在背景從 wunderui.com 取得更新的設計資料;可設定 WUNDERUI_OFFLINE 避免連網。免費方案使用者應只使用標記為 free 的元件。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 WunderUI,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

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.

bash
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

ToolWhat the agent gets
list_componentsThe inventory, filterable by category, plan (free or pro) or free text
get_componentExports, the TypeScript prop signature, the import line, an example, the docs URL
get_tokensLight and dark tokens as JSON, a CSS block, or Tailwind @theme mappings
get_design_mdThe full DESIGN.md, or one section (rules, donts, tasks, tokens, inventory, reference, templates, starters)
list_templatesThe full-page templates and what each is built from
get_starterCopy-paste TSX: app shell, dashboard, data grid, AI chat, theming
get_library_infoPackage name, version, install commands, stack, counts, data source
get_instructionsThe short, always-on rules (components, tokens, motion, copy) for CLAUDE.md / AGENTS.md
list_skillsThe WunderUI agent skills, free and Pro
get_skillOne skill's instructions (SKILL.md), so the agent can follow it without installing — Pro skills need WUNDERUI_LICENSE_KEY
get_block_sourceThe 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.

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 URIWhat it holds
wunderui://design-mdThe full DESIGN.md (markdown)
wunderui://design-jsonThe machine-readable design data (tokens, inventory, templates, skills)
wunderui://tokensLight and dark token values
wunderui://instructionsThe short rules for CLAUDE.md / AGENTS.md
wunderui://componentsThe 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

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

Cursor: .cursor/mcp.json

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.

VariableEffect
WUNDERUI_OFFLINE=1never 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

bash
npm installnpm 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.

來源:README.md,提交 17381f2

工具

11

list_components

List WunderUI components

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".

輸入參數planquerycategory

get_component

Get a WunderUI component

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 …).

輸入參數name必填

get_tokens

Get WunderUI design tokens

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.

輸入參數themeformat

get_design_md

Get the WunderUI DESIGN.md

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.

輸入參數section

list_templates

List WunderUI page templates

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.

無需輸入參數。

get_starter

Get a WunderUI starter snippet

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.

輸入參數kind必填

get_library_info

Get WunderUI package info

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

無需輸入參數。

get_instructions

Get the short WunderUI rules

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.

無需輸入參數。

list_skills

List WunderUI agent skills

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.

無需輸入參數。

get_skill

Get a WunderUI agent skill

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).

輸入參數name必填

get_block_source

Get a WunderUI block's source (Pro)

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.

輸入參數block必填screencategory必填

版本歷史

2
  1. v1.2.1最新Nov 1, 2026
  2. v1.1.0Oct 10, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分