see-u-ui-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_componentsA | 列出 see-u-ui 组件库的全部组件（可按 category 过滤）。返回每个组件的 tag、组件名、中英文标题、分组、一句话描述。用于总览或查找组件。 |
| get_component_apiA | 按 tag（如 see-button）返回单个组件的完整 API：props（含类型/必填/默认值/说明）、events（模板绑定名，kebab-case，如 @on-click）、slots。用于生成使用该组件的准确代码。 |
| get_component_examplesA | 按 tag（如 see-button）返回该组件的可用代码示例（标题 + HTML 模板片段）。用于参考真实用法。 |
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 clearly distinct purpose: listing components, getting API details, and retrieving code examples. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (get_component_api, get_component_examples, list_components). No deviations.
Three tools is well-scoped for a UI component library documentation server. They cover overview, detailed API, and examples without being excessive.
The set covers listing, API details, and examples, which are core for component documentation. A minor gap is the lack of a search tool, but it's not critical.