KRDS UI/UX MCP Server
Related Servers
Alternatives to KRDS UI/UX MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides Korean government design system (KRDS) guidelines to AI models via MCP, enabling AI assistants to comply with KRDS standards when developing government websites and digital services.8 npm15MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to retrieve and cite South Korean national construction standards (KDS/KCS) with tables and formula images via the KCSC OpenAPI, and to use design decision trees, validation, and blank Excel templates directly in the chat interface.13MIT
- AlicenseBqualityCmaintenanceProvides AI coding tools with structured access to U.S. Web Design System components, patterns, templates, and accessibility guidance for building government websites.912 npm1MIT
- FlicenseAqualityBmaintenanceEnables searching and retrieving Korean government documents (press releases, policies, laws, statistics, etc.) from about 50 central administrative agencies through natural language interactions with AI assistants like Claude and ChatGPT.112-
- AlicenseNot gradedqualityAmaintenanceUAE Design System (AEGOV DLS) for AI assistants: component catalogue, design tokens, UAE PASS & Emirates ID scaffolds, snippet validation.MIT
- AlicenseAqualityAmaintenanceIt lets AI coding agents look up design tokens, component specifications, and prohibition rules on demand, then validate generated HTML or JSX with the same lint logic used by CI and editor hooks so violations are caught and corrected immediately. It also exposes the design constitution and rule sets as resources for reference during generation.6364 npm201MIT
TDQS
Scored across 9 tools
Every tool has a clearly distinct purpose with no overlap. Tools like get_component_code, list_all_components, and search_krds_components all target components but with different actions (get specific code, list names, search/filter), making them easily distinguishable. The descriptions clearly differentiate between fetching, listing, searching, and validating operations.
All tool names follow a consistent verb_noun pattern in snake_case, such as get_color_palette, list_all_components, and search_design_tokens. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 9 tools, the count is well-scoped for a UI/UX design system server. Each tool serves a specific purpose in accessing and managing design resources, components, and compliance, without feeling excessive or insufficient for the domain.
The tool set covers core operations for a design system, including fetching resources, listing/searching components and tokens, and validating compliance. A minor gap exists in update or modification tools (e.g., for editing components or tokens), but agents can work around this with the provided read and validation tools.