A
licenseA
qualityC
maintenanceProvides AI coding assistants with on-demand access to component specs, test scenarios, accessibility requirements, and build guides from the Web UI Component Specification.
10
MIT
Components Build MCP
by getlokiui
Related Servers
Alternatives to Components Build MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables an AI assistant to describe a screen by its object and context and receive generated React or Vue code built from governed components and design tokens. It also renders charts from supplied data, produces receipts of static checks, and offers an optional tool that verifies contrast pairs and document accessibility rules across built brands and themes.2Apache 2.0
- FlicenseAqualityDmaintenanceProvides AI assistants with direct access to shadcn/ui components and blocks, enabling real-time fetching of component source code, documentation, and implementation examples.419 npm4-
- AlicenseAqualityDmaintenanceProvides access to 77 pre-built, accessible Basecoat CSS UI components across forms, navigation, feedback, interactive, and layout categories, enabling AI assistants to retrieve HTML components and usage documentation for building user interfaces.726 npm4MIT
- FlicenseAqualityDmaintenanceProvides AI assistants with frontend development tools including component scaffolding, bundle analysis, accessibility checks, and responsive design guidance. Enables automated generation of React components with tests and stories, bundle optimization recommendations, and WCAG compliance fixes.6-
- AlicenseBqualityCmaintenanceEnables AI-powered generation, customization, and documentation of its-just-ui React components. Provides tools for component generation, theme management, form creation, responsive layouts, and accessibility guidance.9148 npm4MIT
TDQS
B3.4/5.0
Scored across 11 tools
Disambiguation4/5
Most tools have distinct purposes, but there is some overlap between get_rules and list_rules, as both deal with rules documentation, which could cause confusion. However, descriptions clarify that get_rules provides detailed documentation with filtering, while list_rules offers a summary list, helping to mitigate ambiguity.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern throughout, such as check_compliance, generate_component, get_quick_reference, and grade_component. This predictability makes it easy for agents to understand and select tools without confusion.
Tool Count5/5
With 11 tools, the server is well-scoped for its purpose of component development and compliance. Each tool serves a specific function, from generating and grading components to accessing documentation, ensuring a comprehensive toolset without being overwhelming.
Completeness4/5
The tool surface covers key aspects like component generation, compliance checking, grading, and extensive documentation access. A minor gap is the lack of tools for updating or deleting components, but agents can likely work around this given the server's focus on development and compliance rather than full lifecycle management.
Maintenance
ActivityInactive
ResponsivenessNo issues