perfectui-mcp
Related Servers
Alternatives to perfectui-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides a real API for coding agents to look up design system components, props, and tokens, preventing guessed answers.9MIT
- AlicenseAqualityCmaintenanceEnables AI coding agents to set up the kit and build pages with it by serving each release's own docs data: searching and describing components, producing install code for a given setup, returning class and content conventions, and checking pages for unknown classes, hooks and missing files. It reads only public docs, with no sign-in or stored data.5BSD 3-Clause
- AlicenseAqualityDmaintenanceProvides programmatic access to Material Web documentation and components for AI agents, enabling documentation search, template generation, and HTML validation.718 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to ground UI work in real product screens by searching a catalogue for concrete screen references and design materials such as fonts, icons, and animated icons, then pulling the colors, typography, components, and provenance behind a chosen web screen. It also serves bundled skill documents, command playbooks, and connection diagnostics so an agent can settle a screen's states and acceptance criteria before building and verify the rendered result afterward.MIT
- AlicenseAqualityCmaintenanceProvides AI coding assistants with on-demand access to component specs, test scenarios, accessibility requirements, and build guides from the Web UI Component Specification.10MIT

@vaneui/mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to read VaneUI's component reference, guides, and per-component prop tables on demand, and to search the full docs corpus for prop names, defaults, and Tailwind class mappings.495 npm1MIT
TDQS
Scored across 5 tools
get_install and get_component both retrieve documentation content for installation, but get_install is a specialized shortcut for install commands while get_component returns full Markdown of any document; descriptions clarify the boundary. Other tools (list_components, search_docs, check_markup) have clearly distinct purposes. Minor overlap prevents a perfect score.
All tool names follow a consistent snake_case verb_noun pattern (get_install, list_components, search_docs, get_component, check_markup). This makes the set predictable and easy to parse.
Five tools cover the essential operations for a UI library documentation server: installation lookup, listing documents, searching, retrieving a document, and validating markup. Each tool has a clear role and the set is well-scoped.
The surface covers installation, discovery (list, search), retrieval, and validation, including legacy class migration. No obvious dead ends for the stated purpose of helping agents use Perfect UI correctly; the documentation lifecycle is fully covered.