mcp-lanhu
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
} |
| 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
The three tools have clearly distinct purposes: resolving invite links, working with designs, and working with pages. Even with modes inside design and page, the resource type separation is unambiguous.
All tools share the lanhu_ prefix, but lanhu_resolve_invite_link uses a verb_noun pattern while lanhu_design and lanhu_page are plain nouns. The naming is readable but not fully consistent in verb usage.
Three tools is a reasonable count, though the design and page tools bundle many modes, making them somewhat overloaded. Still, the scope is manageable and each tool earns its place.
The surface covers listing, analyzing, extracting tokens, downloading slices, and resolving links—all common read-only operations for a design tool. Missing create/update operations, but that may be intentional for a design inspection server.