Lanhu MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LANHU_COOKIE | Yes | 蓝湖的 Cookie。获取方式：登录蓝湖 (lanhuapp.com) → F12 → Network → 复制任意请求的 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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lanhu_resolve_invite_linkB | Resolve Lanhu invite/share link to actual project URL with tid/pid/docId parameters. |
| lanhu_designA | Unified Lanhu design tool. Supports listing, analyzing, extracting tokens, and getting slices. Modes:
For detailDetach URLs (contains image_id), pass design_names='all'. |
| lanhu_pageB | Unified Lanhu PRD/prototype tool. Supports listing and analyzing pages. Modes:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| frontend-dev | Analyze a Lanhu design and generate pixel-accurate frontend code |
| design-review | Review a Lanhu design for consistency and implementation feasibility |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
lanhu_design and lanhu_page both have 'list' and 'analyze' modes, which could cause confusion. Their names distinguish designs from pages, but the modes overlap. lanhu_resolve_invite_link is clearly distinct.
Two tools follow a noun-based pattern (lanhu_design, lanhu_page) while the third uses a verb phrase (lanhu_resolve_invite_link). The naming is mostly consistent but the third tool breaks the pattern.
3 tools is reasonable for a design collaboration server, covering design assets, pages, and link resolution. It could potentially be expanded, but it's not too few.
The server covers design listing/analysis, page listing/analysis, and link resolution. Missing are operations like creating or updating designs/pages, or managing slices directly. Core viewing and analysis are covered.