Your agent can read WunderUI
Most of the code written with a component library today is written by an agent that has never seen its documentation. WunderUI ships the same design system four more times — as an MCP server, a markdown document, structured data and an llms.txt — so the agent works from the real API instead of guessing.
Components described
201
Categories
8
Page templates
5
Why it exists
Ask an agent for a data table and it writes one from scratch: raw divs, invented class names, a color it picked itself. Not because it is careless, but because nothing told it that exists, takes a array and already handles sorting, search and selection.
Everything on this page answers that one question — what exists, what it takes, and which token to use — in whatever form the tool at hand can consume.
What ships
Pick by what your tool speaks. They carry the same content from the same source.
MCP server
Seven tools that let an agent search the inventory, read prop signatures, pull tokens and drop in a starter — inside the editor, without leaving the task.
Claude Code, Cursor, Windsurf, Codex, VS Code, Cline
DESIGN.md
The whole design system as one markdown document: install steps, the rules an agent should follow, every token, the component inventory and starter snippets.
Any chat or agent that takes pasted context
design.json
The same content as structured data — tokens, components with exports and prop signatures, templates — for your own scripts, checks and tooling.
Build scripts, CI, custom tooling
llms.txt
The llms.txt convention: a short, link-dense index of every component and template, for crawlers and assistants that discover a site on their own.
Crawlers, search and discovery agents
Agent skills
A whole job for your agent, not one answer.
Quick start
One line in Claude Code, and the agent can search the library while it works:
claude mcp add wunderui -- npx -y @wunderui/mcpNo editor with MCP support? Paste the design context at the top of your prompt instead:
curl -s https://wunderui.com/DESIGN.md | pbcopyHow it stays current
Nothing here is written by hand. A generator reads the library source on every release and rewrites all four artifacts, so the props an agent sees are the props the build actually exports.
| Source in the repo | Becomes |
|---|---|
| Design tokens, light and dark | |
| Exports and prop signatures | |
| Names, categories, descriptions | |
| The page templates |
npm run build:react # dist/index.d.ts must be current
npm run generate:agent-context # rewrites DESIGN.md, design.json, llms.txt and the MCP dataFree to use
All four artifacts are public and free, whether or not you own a license. They describe the library and cost nothing to read. The free components are MIT; the license covers the Pro components, UI Blocks and templates. The MCP server runs locally over stdio: no key, no account, no network call. The agent skills above are the one exception: they are part of WunderUI Pro and come with the purchase.