tkh-components
Related Servers
Alternatives to tkh-components
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables coding agents to search and retrieve 500+ production-ready React and Tailwind UI sections, page recipes, and brand-styled components over MCP, along with imagery and social post templates.-
- AlicenseNot gradedqualityDmaintenanceProvides resources, tools, and prompts for a Design System via MCP protocol, enabling component search, reading, and related component discovery.284 npmMIT
- AlicenseAqualityFmaintenanceComprehensive MCP server for end-to-end UI development, offering tools to generate components, manage design tokens, audit accessibility, autofix issues, inspect live pages, compare screenshots, and more across multiple frameworks.1311 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceMCP server for the NS UI React component registry. Search components, inspect source and details, list categories, get install commands, and retrieve design-token conventions.3 npm31MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to search, discover, and retrieve UI HUB components, source code, dependencies, templates, and animations via MCP.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to read a project's component tree and design tokens, edit React/TSX canvas frames, set props, apply auto layout and variants, add shader backgrounds, and capture screenshots, so agents can make design changes that are written back as reviewable code diffs and pull requests.2MIT
TDQS
Scored across 7 tools
Most tools are clearly distinct (get_component for one item, get_design_tokens, get_design_spec, get_site_content, render_page all target different resources). search_components and list_components overlap slightly since list can filter by category while search does keyword matching, but the descriptions clarify the boundary.
Consistent snake_case verb_noun pattern throughout: search_components, list_components, get_component, get_design_tokens, get_design_spec, get_site_content, render_page. The 'get_' family and the search/list/render verbs are used predictably.
Seven tools is well-scoped for a component-library/reference server, with each tool earning its place (discovery, retrieval, tokens, spec, content, composition). No redundant or thin entries.
The read-and-compose surface is strong: discovery (search/list), retrieval with multiple output formats (get_component), design system data (tokens/spec/content), and page composition (render_page). There is no write/create/update path for components, but the server's apparent purpose is serving reference components, so this is a minor gap.