A
licenseNot graded
qualityC
maintenanceThis MCP server provides tools to install and manage shadcn/ui components directly from AI coding agents.
2
MIT
encode-ui
by reuvenaor
Related Servers
Alternatives to encode-ui
No user-submitted related servers found.
Related Servers
- 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.4876 npm60MIT
- AlicenseAqualityCmaintenanceMCP server for Shadcn Dashboard that enables AI to discover, search, and install UI blocks directly into projects without copy-paste.6361 npmMIT
- AlicenseAqualityBmaintenanceA secure MCP server that gives AI coding assistants direct access to the shadcn/ui registry, enabling fetching, installing, and wiring up components without switching context.814 npm4MIT
- AlicenseAqualityDmaintenanceA mcp server to allow LLMS gain context about shadcn ui component structure,usage and installation102,148 npm2,989MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive template for building MCP servers that expose UI component registries and design systems to AI assistants. It enables users to browse, fetch, and retrieve implementation details from registries following the shadcn/ui format.22 npm2MIT
TDQS
A4.5/5.0
Scored across 8 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: searching, finding similar, fetching metadata, fetching source, listing groups, listing components, getting install commands, and finding icons. The descriptions explicitly clarify differences (e.g., search_components vs list_components), so there is no ambiguity.
Naming Consistency4/5
Most tools follow a verb_noun pattern (search_components, get_component, list_groups, list_components, find_icons). Minor deviations include find_similar (verb + adjective) and compound nouns like get_component_source and get_install_command, but these are still readable and predictable.
Tool Count5/5
With 8 tools, the set is well-scoped for a component registry server. Each tool covers a distinct aspect of discovery and installation without redundancy, fitting the typical 3-15 tool sweet spot.
Completeness5/5
The tool surface covers the full read/install workflow: searching, browsing by group, enumerating, getting metadata, getting source, getting install commands, and verifying icons. No obvious gaps exist for the server's stated purpose of exploring and installing components.
Maintenance
ActivityActive
ResponsivenessNo issues