uikit-registry
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UIKIT_DATA_DIR | No | Path to the data directory containing component library data (default: ./data) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_componentA | Cari komponen UI di semua library. Return daftar library yg punya komponen itu. |
| get_componentA | Ambil detail komponen dari library tertentu. Dapat source code (shadcn) atau props + contoh (MUI, Chakra, dll). |
| compare_componentsA | Bandingkan komponen yang sama dari dua atau lebih library. Melihat perbedaan props, import path, dan source code. |
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 3 tools
Each tool has a distinct purpose: search finds components across libraries, get retrieves details from a specific library, compare contrasts same component across libraries. No overlap.
All tool names follow a consistent verb_noun pattern (compare_components, get_component, search_component) with snake_case.
Three tools is appropriate for a focused UI component registry, covering search, retrieval, and comparison without unnecessary bloat.
Covers core operations well, but a tool to list all libraries or components directly might be missing; however, search can approximate this.