moonvy-ui-mcp
Related Servers
Alternatives to moonvy-ui-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables developers to extract and organize Figma design files, including complete node data (tree structure and images) for AI understanding and code generation.23 PyPIMIT
- AlicenseCqualityBmaintenanceEnables AI clients to import and inspect Figma designs, read properties, styles, components, and variables, download screens and assets, and validate screenshots against offline snapshots.201MIT
- AlicenseAqualityNot gradedmaintenanceEnables interaction with Figma files through intelligent API access, providing navigation, asset extraction, and design token retrieval with 95% token-optimized compact tree output format.151MIT
- AlicenseCqualityBmaintenanceEnables 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.231MIT
- AlicenseAqualityCmaintenanceProvides AI coding agents with structured access to Lanhu design data, enabling direct inspection of artboards, extraction of pixel-perfect layer styles and CSS attributes, and downloading of design assets without vision token overhead.9MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI apps to open, inspect, modify, render, and save local Figma files—including Design, Slides, FigJam, and Sites—without a Figma account, app, or API limits, and to turn designs into code using exact values.1MIT
TDQS
Scored across 10 tools
Each tool has a distinct responsibility: URL parsing, listing pages, fetching design metadata, layer indexing, node style extraction, tree traversal, token extraction, full spec generation, asset download, and cache management. No two tools overlap in purpose, making misselection unlikely.
All tools follow a consistent 'moonvy_verb_noun' pattern using snake_case (e.g., moonvy_list_pages, moonvy_get_node_style). The prefix uniformly identifies the server, and verbs are action-oriented with descriptive nouns, creating a predictable and readable API surface.
With 10 tools, the server covers the core workflow of navigating Moonvy designs, extracting styles, tokens, specs, and assets without excess. The count is well-scoped for its purpose—neither too sparse nor bloated.
The tool surface covers the full design-to-code pipeline: parse URLs, navigate hierarchy, retrieve detailed node styles, extract tokens, generate UI specs, and download assets. A minor gap is the lack of tools for editing or creating designs, but given the read-focused nature of this server, the existing set is comprehensive and leaves no dead ends for typical usage.