lanhu-ui
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LANHU_COOKIE | Yes | 完整的Cookie，从浏览器开发者工具复制 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lanhu_ui_regionC | Return exact elements plus flow/flex/grid-first implementation guidance. |
| lanhu_ui_assetsC | Download the exact cuts shown by Lanhu's cut-away mode. |
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 2 tools
The two tools are clearly distinct: one provides region and implementation guidance, the other handles asset downloads. No overlap.
Both tools follow a consistent snake_case pattern with 'lanhu_ui_' prefix and a noun indicating the resource (region, assets).
With only 2 tools, the server feels very thin. While it may serve a narrow purpose, most similar servers offer more operations.
The server covers only two aspects of UI design interaction. Missing obvious tools like listing regions, getting design specs, or other common operations.