Lanhu MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATA_DIR | No | Managed Packet and downloaded-asset cache. | ./data |
| DDS_COOKIE | No | Optional Cookie sent only to the configured DDS host and subdomains. | |
| SERVER_HOST | No | HTTP bind host; only loopback addresses are accepted. | 127.0.0.1 |
| SERVER_PORT | No | HTTP port. | 8126 |
| DDS_BASE_URL | No | Advanced HTTPS-only endpoint override. | |
| HTTP_RETRIES | No | Retry count, from 0 to 3. | 3 |
| HTTP_TIMEOUT | No | Positive request timeout in seconds. | 30 |
| LANHU_COOKIE | No | Cookie sent only to the configured Lanhu host and subdomains. | |
| MCP_TRANSPORT | No | http or stdio. | http |
| LANHU_BASE_URL | No | Advanced HTTPS-only endpoint override. | |
| MAX_ASSET_BYTES | No | Maximum bytes per downloaded asset. | 52428800 |
| UNITY_TEXT_FONT_GUID | No | Optional default UGUI Font GUID from an imported .ttf/.otf. | |
| MAX_NODES_PER_RESPONSE | No | Maximum node count for a full response. | 200 |
| MAX_PACKET_ASSET_BYTES | No | Maximum aggregate downloaded bytes per Packet. | 524288000 |
| UNITY_TEXT_FONT_MAP_JSON | No | Optional inline source-font-name to UGUI Font GUID map. | |
| UNITY_TEXT_FONT_MAP_PATH | No | Optional path to a UTF-8 UGUI font map JSON file. | |
| ASSET_DOWNLOAD_CONCURRENCY | No | Download workers, from 1 to 16. | 4 |
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_list_designsA | List the design pages available in a Lanhu project. |
| lanhu_prepare_designB | Fetch, normalize, download, validate, and atomically store one Lanhu design. |
| lanhu_inspect_designA | Inspect a prepared design packet through a compact task-oriented view. |
| lanhu_generate_unity_prefabC | Generate a staged, verified UGUI prefab snapshot for a supported Unity LTS project. |
| lanhu_verify_unity_prefabB | Statically verify generated prefab YAML, ownership metadata, source map, sprites, and file ids. |
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 5 tools
Each tool maps to a distinct stage in the design-to-prefab pipeline: listing, preparing, inspecting, generating, and verifying. The overlap between list_designs and inspect_design is minimal because one targets project pages and the other targets prepared packets.
All tools share the lanhu_ prefix and follow a consistent snake_case verb_noun pattern. The verbs list, prepare, inspect, generate, and verify clearly indicate the action while the nouns identify the target artifact.
Five tools is well-scoped for a focused design-to-Unity-prefab workflow. Each tool has a clear purpose and no redundant operations clutter the surface.
The tool set covers the full lifecycle from discovering available designs, preparing and inspecting them, to generating and verifying a Unity prefab. There are no obvious dead ends or missing critical operations for the stated domain.