lanhu-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lanhu_set_cookieA | 设置蓝湖认证 Cookie（并持久化到 ~/.lanhu/cookie）。 一般无需手动调用：Cookie 文件由 scripts/refresh_cookie.py 自动维护， MCP 启动时自动读取。仅在自动刷新不可用时，才需要从浏览器手动复制： DevTools → Network → 任一 lanhuapp.com 请求 → Request Headers → 复制完整 Cookie 头（须含 session 和 user_token）→ 传给本工具。 设置后可调用 lanhu_get_teams 验证是否生效。 |
| lanhu_get_teamsA | 获取当前登录用户所在的团队列表。也可用于验证认证是否有效。 |
| lanhu_get_projectsB | 获取团队下的设计项目列表。 |
| lanhu_search_projectsB | 在团队下按名称关键词搜索项目。 |
| lanhu_get_screensA | 获取指定项目下的所有设计图（画板）列表，返回缩略图与尺寸信息。 |
| lanhu_get_annotationsA | 获取单张设计图的完整标注数据（最核心的工具）。 返回内容包含：
|
| lanhu_search_imagesC | 在指定项目中按名称关键词搜索设计图。 |
| lanhu_get_assetsB | 获取设计图中所有可下载的切图/图标资源列表（含 svg/png 直链）。 |
| lanhu_download_assetA | 下载指定的切图/图标到本地文件（位图默认自动转为 WebP 格式），返回保存路径。 需要先调用 lanhu_get_assets 获取资源的 download_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 9 tools
Several tools have overlapping retrieval surfaces: get_projects vs search_projects and get_screens vs search_images are list-vs-search pairs, and get_annotations already includes downloadable assets that get_assets re-exposes. Descriptions clarify the intended use, but an agent could still select a broader tool when a narrower one is needed.
All tools share the lanhu_ prefix and follow a consistent verb_noun snake_case pattern (set_, get_, search_, download_), with no mixed conventions or vague generic names.
9 tools is well-scoped for a design-handoff/annotation server: auth, team/project navigation, screen listing, annotation retrieval, and asset download each have a focused tool.
The read-only workflow is well covered: authenticate, navigate teams/projects/screens, fetch annotations, and download assets. Minor gaps such as no direct get-by-id for a single project/screen (relying on list/search) and the redundant asset list inside get_annotations keep it from a perfect score.