UI libraries with an MCP server

An MCP server lets your coding assistant read a library's real documentation instead of recalling it from training data. That matters most at version boundaries, where an assistant working from memory writes confident code against an API that no longer exists: Chakra v2 to v3, Fluent v8 to v9, NextUI to HeroUI. Depth varies a lot, so read each entry rather than treating the badge as equal everywhere. Some expose documentation only; shadcn/ui makes its server registry-aware, HeroUI runs a second one just for migrations, and Mantine adds agent skills on top. One pattern is worth noticing: the headless primitive layers publish almost none of these.