lanhu-mcp-codex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LANHU_COOKIE | Yes | Cookie from Lanhu request headers |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lanhu_parse_urlA | Parse a Lanhu project/design URL into pid, tid, image_id, doc and route fields. |
| lanhu_list_project_imagesB | Read a Lanhu project's design image list. This tool is read-only and does not write files. |
| lanhu_get_design_contextC | Generate local context.md/context.json and optional thumbnail files from a Lanhu URL. |
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 3 tools
Each tool has a clearly distinct purpose: one generates context files, one lists images (read-only), and one parses URLs. No overlap.
All tools follow the consistent pattern 'lanhu_verb_noun' with snake_case, using clear verbs (get, list, parse).
3 tools is slightly on the low side but appropriate for a focused domain like Lanhu design integration; each tool earns its place.
Covers basic operations (parse, get context, list images) but lacks tools for individual image details or design updates, leaving notable gaps.