ui-registry-mcp
Related Servers
Alternatives to ui-registry-mcp
No user-submitted related servers found.
Related Servers
- 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-
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to search, inspect, and retrieve real UI components from existing component libraries, with ranked results, score explanations, licence and provenance details, and safe installation plans. It also surfaces similar components and higher-level UI patterns so agents can reuse existing interface code instead of generating it from scratch.44 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to search a fully local catalog of 21st-style shadcn components via full-text search, inspect individual records, generate reusable build prompts, retrieve install steps, and fetch design tokens for aesthetic keywords. Runs entirely offline over stdio with no API keys, paywalls, or rate limits.Apache 2.0
- AlicenseAqualityDmaintenanceProvides AI assistants with comprehensive access to shadcn/ui v4 components, blocks, demos, and metadata across React, Svelte, Vue, and React Native, enabling efficient component integration and code generation.108,219 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to search across 340+ React UI registries, inspect component code and quality scores, compare options, detect a project's stack, and generate or execute safe transactional install plans. It provides read and write safeguards with dry-run planning and rollback.1MIT
- AlicenseAqualityDmaintenanceHelps AI assistants access shadcn/ui component documentation and examples through a TypeScript-based MCP server that provides reference information for component details, usage examples, and search capabilities.4651 npm60MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing registries, searching components, fetching full component source, comparing alternatives across libraries, and checking design consistency. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern with underscores (e.g., list_registries, search_components, get_component, compare_components, check_consistency). There is no mixing of naming conventions.
With 5 tools, the surface is well-scoped for the server's purpose: discover libraries, search and retrieve components, compare options, and validate consistency. Each tool earns its place without being excessive or insufficient.
The tool set covers the full workflow from listing registries to searching, retrieving, comparing, and checking consistency. There are no obvious gaps for the intended use case of exploring and integrating UI components from multiple registries.