Lanhu MCP Server: Setup for Claude, Cursor and Other Apps

• Lists the pages of a Lanhu requirement prototype

  Opens a Lanhu Axure document link and returns its page list. The assistant must call this before it analyzes a requirement document.

  Try: “Look at this Lanhu requirement link and list its pages.”

  Write · lanhu_get_pages

• Reads requirement pages as text and screenshots for analysis

  Pulls the text, notes and rendered images of chosen prototype pages in stages, from the developer, tester or quick-scan point of view. Pages and images are cached on disk after the first read.

  Try: “Analyze the order page of this Lanhu document for test cases.”

  Write · lanhu_get_ai_analyze_page_result

• Zooms into one spot of a requirement page

  Finds a phrase or area on a rendered prototype page and returns a clear crop around it, so small fields stay readable. When a phrase matches several places it returns previews of each instead of guessing.

  Try: “Show me the area around the red box that mentions the refund limit.”

  Files · lanhu_inspect_requirement_region

• Lists the requirement documents in a Lanhu project

  Returns every product document or prototype in a project, so you can pick one before you ask for its pages.

  Try: “What requirement documents are in this Lanhu project?”

  Network · lanhu_list_product_documents

• Turns a Lanhu invite link into a project link

  Converts a Lanhu invite or share link into the project address and ids the other tools need.

  Try: “Open this Lanhu invite link and tell me which project it points to.”

  Network · lanhu_resolve_invite_link

• Lists the UI design images in a Lanhu project

  Returns the design screens in a project with their ids. Call it first, then pass an id to the design tools.

  Try: “List the UI designs in this Lanhu project.”

  Write · lanhu_get_designs

• Snapshots one UI design with a numbered map of its layers

  Fixes one design version, returns an image of it, and lists its layers with stable numbers. Use it before you zoom into parts of a design.

  Try: “Give me an overview of the login screen design.”

  Write · lanhu_get_design_overview

• Crops part of a design with its exact styles and asset ids

  Returns a clear crop of a chosen area or layers of a design, with each layer's source styles and linked asset ids. Use it to get exact sizes, spacing, colors and fonts.

  Try: “Crop the header of this design and give me its sizes and colors.”

  Write · lanhu_inspect_design_region

• Shows a whole design with a draft HTML and CSS reference

  Older tool that previews a full design and builds a draft HTML and CSS reference from its data. The generated code is only a hint, and the project prefers the overview and region tools for exact evidence.

  Try: “Show this design with a first HTML and CSS draft.”

  Write · lanhu_get_ai_analyze_design_result

• Lists the slices and icons in a design for download

  Finds the cut-out images, icons and other assets in a design and downloads them to the server's data folder with readable names.

  Try: “Get the icons and slices from this design.”

  Write · lanhu_get_design_slices

• Exports original design assets as a ZIP with a manifest

  Downloads the original design assets you pick, checks their size and hash, and delivers a ZIP with a manifest. It never upscales images.

  Try: “Export the three icons I selected as a ZIP.”

  Write · lanhu_export_design_assets

• Posts a note to the team's shared message board

  Writes a message on the project's board that other people's assistants can read. A message can be a normal note, a task to look something up, a question, or shared know-how, and it can @mention teammates.

  Try: “Tell Li Si that the refund rule on the order page conflicts with the design.”

  Write · lanhu_say

• Lists and searches messages on the team board

  Returns the board's messages for one project or for all projects, filtered by type or search text. It works best with a filter so it does not flood the assistant's context.

  Try: “Which messages on the board mention me?”

  Write · lanhu_say_list

• Reads the full text of chosen board messages

  Returns the complete content of one or several messages by their ids.

  Try: “Show me the full text of message 12.”

  Write · lanhu_say_detail

• Edits a message on the team board

  Changes a message that was posted before, and records who edited it and when.

  Try: “Fix the typo in my last board message.”

  Write · lanhu_say_edit

• Deletes a message from the team board

  Removes a posted message from the board. This only touches the board kept by this server, not your Lanhu documents.

  Try: “Delete my old message about the login page.”

  Delete · lanhu_say_delete

• Lists who has used the server on a project

  Shows the people whose assistants accessed this project through the server, with their first and last access times. The server builds this list itself by saving each caller's name and role in a local file.

  Try: “Who has looked at this project's documents?”

  Write · lanhu_get_members

Watch out for

• It can delete message board posts

  The delete tool removes posted messages from the server's team board. It does not delete anything in Lanhu itself. github.com

• HTTP mode listens on every interface with no sign-in

  The server starts in HTTP mode unless you pass --transport stdio or set MCP_TRANSPORT=stdio, and its default address is 0.0.0.0 on port 8000. It has no sign-in of its own, so anyone who can reach the port can use your Lanhu cookie to read your documents and post or delete board messages. Use the stdio setup, or set SERVER_HOST to 127.0.0.1. github.com

• It uses your full Lanhu login cookie

  LANHU_COOKIE is your whole Lanhu browser session, not a limited token, so the server can open everything your account can and it works until the session expires. It is stored as plain text in the .env file in the cloned folder. Keep that file out of repos and log out of Lanhu to invalidate the cookie if it leaks. github.com

• It saves pages, images and exports to disk

  Design and requirement downloads are cached in a data folder next to the project. Clear it when you finish with a project. github.com

• Every call logs your name and role to disk

  Most tools save the caller's name and role, with first and last access times, in a JSON file in the data folder, which lanhu_get_members then lists to anyone using the same server. github.com

Security advisories