F
licenseA
qualityD
maintenanceProvides AI assistants with direct access to shadcn/ui components and blocks, enabling real-time fetching of component source code, documentation, and implementation examples.
4
17 npm
4
-
shadcn-ui-mcp-server
Related Servers
Alternatives to shadcn-ui-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to access and manage shadcn/ui v4 components, including source code, demos, blocks, and CLI integration.1225 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to discover, install, and generate code examples for shadcn/ui components, providing installation commands and usage examples for 37+ React UI components.MIT
- 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.4609 npm60MIT
- AlicenseAqualityDmaintenanceProvides reference information for shadcn/ui components through a Model Context Protocol server that helps AI assistants access component documentation and examples.4609 npmMIT
- AlicenseAqualityCmaintenanceProvides coding agents live access to shadcn-style component registries, enabling them to search, compare, and fetch real component source code for UI composition.565 npm5MIT
TDQS
A3.7/5.0
Scored across 10 tools
Disambiguation5/5
Each tool targets a distinct resource (component, block, theme, directory) and action (list, get, apply). The three component-specific getters are clearly separated by what they return: source, demo, or metadata, so an agent is unlikely to confuse them.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with snake_case: list_* for enumeration, get_* for retrieval, and apply_theme for the one mutation. Singular get_* versus plural list_* is a standard and predictable convention.
Tool Count5/5
Ten tools is well-scoped for the server's purpose. The three resource domains (components, blocks, themes) each have a small, focused set of tools, and no tool feels redundant or unnecessary.
Completeness4/5
The tool surface covers the core workflows: discovering components and blocks, retrieving their source/demo/metadata, and exploring/applying themes. Minor gaps exist (e.g., no search/filtering across components, no block demos or metadata), but an agent can accomplish most expected tasks without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues