Plumb (plumb-mcp)
Related Servers
Alternatives to Plumb (plumb-mcp)
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceConverts Figma designs into structured code context with token-aware styling, enabling AI agents to generate production-level frontend code.111 npmMIT
- AlicenseNot gradedqualityDmaintenanceConnects Figma designs to AI agents, enabling extraction of production-ready code, assets, and design tokens through natural language descriptions. Supports React, Vue, CSS, and Tailwind with real-time design system analysis.83,854 npm40MIT

@forgespace/ui-mcpofficial
AlicenseBqualityFmaintenanceEnables AI-driven generation of UI components, full applications, and backend code across multiple frameworks (React, Vue, Angular, Svelte, HTML) with Figma integration and brand identity support.3837 npm2MIT- FlicenseAqualityCmaintenanceEnables AI assistants to generate production-ready, professional UI design systems and components from simple descriptions, with real images, animated components, and automated quality checks.16-
- FlicenseBqualityBmaintenanceEnables coding agents to read, render, and normalize design documents from Figma and Adobe XD, providing visual context plus structured design data and generating starter code for web, React, Vue, Flutter, SwiftUI, and Jetpack Compose.131-

producer-cueofficial
FlicenseAqualityBmaintenanceEnables AI coding assistants to design, synthesize, heal, and export production-ready accessible web applications and design systems in real time with zero build overhead.7-
TDQS
Scored across 28 tools
Each tool has a distinct, well-defined purpose. Even closely related tools like plumb_verify and plumb_fit are clearly differentiated (one-time check vs. iterative loop). The descriptions are precise, leaving no ambiguity about when to use each tool.
All tools follow the consistent 'plumb_' prefix with a descriptive noun or compound noun (e.g., plumb_outline, plumb_fig_node, plumb_studio_start). No mixing of conventions, making it easy to predict tool names.
28 tools is appropriate for the broad scope of Figma design workflow automation. Each tool covers a specific operation without overlap, and the count reflects the complexity of the domain without being excessive.
The tools cover the full design lifecycle: extraction, search, export, diff, audit, code generation, and even design creation back into Figma. There are no obvious gaps; the set supports both read and write directions comprehensively.