@jpisnice/shadcn-ui-mcp-server
Related Servers
Alternatives to @jpisnice/shadcn-ui-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceThis MCP server provides tools to install and manage shadcn/ui components directly from AI coding agents.2MIT
- AlicenseAqualityBmaintenanceMCP server that lets AI agents search and inspect shadcn components from the encode-ui registry, returning metadata, source code, and install commands.8244 npmMIT
- 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.64 npm2MIT
- 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.4372 npm60MIT
- AlicenseAqualityCmaintenanceMCP server for Shadcn Dashboard that enables AI to discover, search, and install UI blocks directly into projects without copy-paste.646 npmMIT
- AlicenseAqualityDmaintenanceProvides reference information for shadcn/ui components through a Model Context Protocol server that helps AI assistants access component documentation and examples.4372 npmMIT
TDQS
Scored across 10 tools
Each tool targets a distinct resource: theme, block, component, or directory structure. The get_component, get_component_demo, and get_component_metadata are clearly differentiated by what they return (source, demo, metadata). No tools overlap in purpose.
All tool names follow a consistent verb_noun pattern with snake_case: apply_theme, get_block, get_component, get_component_demo, get_component_metadata, get_directory_structure, get_theme, list_blocks, list_components, list_themes. No deviations or mixed conventions.
10 tools is well-scoped for a shadcn/ui reference server. It covers listing and retrieving components, blocks, and themes, plus applying a theme and fetching directory structure. Neither too sparse nor too heavy.
The tool surface fully covers the intended domain: components (list, get source, get demo, get metadata), blocks (list, get), themes (list, apply), and repository structure. There are no obvious gaps for a reference and theme-application server.