shadcn/ui MCP Server
Related Servers
Alternatives to shadcn/ui MCP Server
No user-submitted related servers found.
Related Servers
- 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.2101,929 npmMIT
- FlicenseAqualityDmaintenanceProvides AI assistants with direct access to shadcn/ui components and blocks, enabling real-time fetching of component source code, documentation, and implementation examples.418 npm4-
- 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
- FlicenseBqualityCmaintenanceEnables AI agents to dynamically install shadcn UI components into a mounted project workspace.1-
- AlicenseAqualityDmaintenanceProvides reference information for shadcn/ui components through a Model Context Protocol server that helps AI assistants access component documentation and examples.4876 npmMIT
- 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
TDQS
Scored across 12 tools
Each tool targets a distinct operation on specific entities: blocks vs components vs repository vs project init/status. No two tools have overlapping purposes, and descriptions clearly differentiate them.
All tool names follow a consistent snake_case verb_noun pattern (e.g., get_block_source, install_component, list_blocks). No mixing of conventions.
12 tools is well within the ideal range (3-15) for a focused server. Each tool serves a clear purpose without redundancy or bloat.
Covers init, listing, retrieval of source/demo/metadata, installation, and repository browsing/search. Minor gap: block metadata is missing (only component has metadata getter), but core workflows are fully supported.