lanhu-design-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
} |
| 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_health_checkA | 返回本地配置状态，不访问网络且不暴露 Cookie 值。 |
| lanhu_get_designsC | 获取项目的所有设计图列表。 |
| lanhu_analyze_designA | 分析指定设计稿并返回平台调整后的 UI 结构。 |
| lanhu_get_design_assetsC | 返回完整设计图与细粒度可下载切图资源。 |
| lanhu_export_ui_contextB | 返回包含资产和分析的完整 Agent UI 还原上下文。 |
| lanhu_auth_loginB | 打开专属 Chrome Profile 进行交互式 Lanhu 登录。 |
| lanhu_auth_statusC | 报告托管认证状态，不含凭据信息。 |
| lanhu_auth_logoutA | 登出并删除托管 Profile，需要 confirm=true 确认。 |
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 8 tools
Each tool has a clearly distinct purpose: authentication (login, status, logout) and design operations (list, analyze, get assets, export context). There is no overlap, and descriptions clarify any potential confusion between get_design_assets and export_ui_context.
All tools follow a consistent 'lanhu_' prefix with a verb_noun pattern (e.g., lanhu_auth_login, lanhu_get_designs, lanhu_export_ui_context). The only deviation is lanhu_health_check, which is still a common compound noun and does not break consistency.
With 8 tools, the server is well-scoped for its domain of authentication and design retrieval/analysis. Each tool serves a necessary function without redundancy, and the count is within the ideal 3-15 range.
The tool surface covers authentication, health, listing, analysis, and asset retrieval. A minor gap is the lack of a dedicated 'get_design' tool for basic design details without analysis, but the list and analysis tools effectively cover this need.