Which UI Component Libraries Ship an MCP Server

Ask a coding assistant to build a Chakra UI form today and there is a good chance it writes Chakra v2. Ask it for a Fluent UI dialog and you may get v8. Ask for NextUI and it will happily produce components from a library that has been renamed.

None of that is the assistant being careless. It is recalling an API from training data, and component APIs move faster than training data does. An MCP server fixes this at the source: it lets the assistant read the library's actual current documentation instead of remembering it.

We checked all 50 libraries in this directory individually. Thirteen publish one.

The libraries that ship an MCP server

Library	Ecosystem	What the server exposes
Mantine	React	Component docs, props, search, plus agent skills
shadcn/ui	React	Registry-aware: browse, search and install
shadcn-vue	Vue	Registry-aware, same model as the React original
Ark UI	React, Vue, Svelte, Solid	One server per framework
React Aria	React	React Spectrum server plus agent skills
HeroUI	React	Two servers: v3 docs, and v2 to v3 migration
Material UI	React	Official docs and code examples
Chakra UI	React	Docs, with setup for Cursor, VS Code and Claude
Ant Design	React	Documented in English and Chinese
Nuxt UI	Vue	Component access for assistants
PrimeVue	Vue	Component documentation
PrimeNG	Angular	Component docs plus Angular API metadata
Untitled UI React	React	Browse, search and install from the editor

The badge does not mean the same thing everywhere

Treating this as a yes-or-no property hides real differences. Roughly, there are four tiers.

Documentation only. The server answers questions about components and props. Material UI, PrimeVue, Ant Design and Chakra UI sit here. This is already the difference between correct code and confident guesswork.

Registry-aware. shadcn/ui and shadcn-vue go further: the server reads the registries declared in your components.json, including your own. An assistant can be told to build a page from your internal design system rather than from generic components.

Framework-aware. Ark UI publishes a separate server per framework, because the same component has different bindings in React, Vue, Svelte and Solid. A single server would have to guess which one you want.

Migration-aware. HeroUI runs a second server carrying only the v2 to v3 migration guides. That is a sharp piece of product thinking: a migration is precisely where an assistant is most likely to invent APIs, because it half-remembers both versions.

Mantine sits above all of these. Its server covers docs, props and search across the whole library, agent skills handle longer tasks like building forms or combobox inputs, and the documentation is regenerated on every release. If you code with an assistant daily, it is the most equipped option in this directory.

Version boundaries are where this actually pays

The value is easiest to see at the points where a library broke with its own past:

• Chakra UI v2 to v3 was a rewrite, not an upgrade. Most Chakra content online still targets v2.
• Fluent UI v8 and v9 are different libraries with different packages. They do not mix.
• NextUI became HeroUI, and v3 raised its floor to React 19 and Tailwind v4.
• shadcn/ui moved to Base UI as the default primitive layer for new projects in July 2026, with Radix still supported.
• Radix Vue became Reka UI in 2025.

Every one of those is a trap for an assistant working from memory. Every one of those library's servers, where it has one, resolves it.

Who does not have one, and why that is interesting

Two patterns stand out in the data.

The headless primitive layers are mostly absent. Radix, Base UI, Bits UI, Reka UI, Kobalte and Melt UI publish none. The exceptions, React Aria and Ark UI, are both backed by larger organisations. The plausible reading is that a headless library has far less surface to document, and its maintainers have put the effort into clean markdown instead.

Svelte and Solid have none at all. Not one library in either ecosystem publishes an MCP server. React has nine, Vue has three, Angular has one. If you work in Svelte or Solid and rely on an assistant, that gap is worth factoring in.

What to do when there is no server

Several libraries without one are still well equipped for agents, just through a different mechanism.

llms.txt files. Bits UI, Kobalte, Skeleton, Element Plus, Quasar, Carbon and Fluent UI all publish one. Point your assistant at the URL and you get accurate, current API surface without any protocol.

Per-page markdown. Bits UI, Mantine and Ark UI serve every documentation page as clean markdown. Ark UI even takes a framework parameter:

curl https://ark-ui.com/llms.txt/components/accordion?framework=vue

A JSON catalogue. Aceternity UI publishes its full component list at ui.aceternity.com/api/components, complete with a lastUpdated timestamp and its declared tech stack. No MCP server, but an agent pointed there gets a current list rather than a guess.

One thing to watch out for

daisyUI publishes its llms.txt not as documentation but as an agent skill file, with alwaysApply: true and an instruction telling the assistant to use daisyUI whether or not you asked for it.

Load it into your editor and it will bias code generation toward daisyUI across unrelated projects. That is useful when it is what you want, and worth removing when it is not. Read what you load.

How to wire one up

Setup is the same shape everywhere: a JSON entry naming the server and how to run it. In an editor that reads mcp.json:

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

Check each library's own documentation for the exact command, since package names and transports differ. Most publish setup instructions for Cursor, VS Code and Claude specifically.

Method

Every library in this directory was checked individually rather than inferred. An absent mention in a library's llms.txt is not evidence of an absent server: three libraries we initially marked as having none, Material UI, Mantine and Chakra UI, turned out to publish one on a page their index file did not reference.

One judgement call is worth stating. Angular Material is listed as not having an MCP server, even though the Angular CLI ships an official one. That server exposes CLI capabilities to assistants, not Material component documentation, so counting it would mislead anyone filtering on this to get reliable component APIs.

Checked August 2026. This is a fast-moving area and we recheck it.