Skip to main content
Glama

Related Servers

Alternatives to lanhu-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding assistants to directly access Lanhu design drafts, generate frontend code, parse PRDs, and download design assets.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read Lanhu design specs — layer trees with per-layer CSS, screenshots, downloadable slices, and review comments — so they can restore UI and generate React/Vue/mini-program code without manual measuring or asset hunting.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding tools to read Lanhu design data and automate Design to Code, including project browsing, layer tree extraction, DDS semantic components, and code generation.
      14
      58 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read Lanhu design collaboration content: extracting and analyzing Axure prototype pages, downloading UI designs and slices, and converting design specs into HTML+CSS for implementation. It also provides a shared team message board so multiple AI tools can reuse requirement analyses and knowledge across projects.
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables AI clients to read design pages, screenshots, original assets, styles, and workflows from Lanhu, Figma, and Mockplus, inspect elements, download resources, and build local page-flow maps.
      23
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI coding clients to turn Lanhu design drafts into implementation context, including HTML/CSS or Tailwind output, sliced asset mappings, design tokens, preview images, and downstream implementation guidance.
      2
      244 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation3/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data