KRDS UI/UX MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_krds_componentsC | KRDS 컴포넌트를 검색합니다. 검색어나 카테고리로 필터링할 수 있습니다. |
| get_component_codeC | 특정 KRDS 컴포넌트의 전체 HTML 코드와 정보를 가져옵니다. |
| list_component_categoriesB | 모든 KRDS 컴포넌트 카테고리 목록을 가져옵니다. |
| list_all_componentsB | 모든 KRDS 컴포넌트 이름 목록을 가져옵니다. |
| search_design_tokensC | KRDS 디자인 토큰을 검색합니다 (색상, 간격, 타이포그래피 등). |
| get_color_paletteC | KRDS 전체 색상 팔레트를 가져옵니다. |
| get_token_statsC | 디자인 토큰 통계 정보를 가져옵니다. |
| validate_krds_complianceC | HTML/CSS 코드를 분석하여 KRDS 가이드라인 준수 여부를 확인하고 개선 제안을 제공합니다. |
| get_krds_resourcesB | KRDS 리소스 파일 경로와 사용법을 가져옵니다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.