Plumb
Related Servers
Alternatives to Plumb
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI coding agents access to Figma design data, enabling pixel-perfect implementation of designs through structured data extraction, image downloads, and design token retrieval.39 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA local-first MCP server that connects AI clients to Figma via a WebSocket bridge and native plugin, enabling deterministic design operations like inspection, creation, mutation, styling, validation, and optimization.1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI coding agents to read and write to a local-first HTML/CSS design canvas, bridging visual design and code generation.1MIT
- AlicenseAqualityDmaintenanceMCP server that gives LLMs deep knowledge of design systems and tokens, enabling intelligent design evolution, token analysis, and designer-to-developer handoffs.3713 npm2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for design decisions during a build, providing live UI/animation library docs (via llms.txt) and a curated knowledge base of UX laws and UI conventions. It enables agents to look up real component APIs and apply design best practices, running locally via stdio or hosted on Vercel.6 npmMIT

desrid-html-to-figmaofficial
AlicenseNot gradedqualityCmaintenanceThis MCP server lets AI agents connect to Figma to read, analyze, create, and modify designs, including elements, styles, assets, and code generation. It works with free Figma accounts and supports parallel multi-agent use across MCP-compatible clients.MIT
TDQS
Scored across 28 tools
Descriptions are unusually detailed and explicitly cross-reference each other (plumb_fit as the loop mirror of plumb_verify, plumb_fig_outline as the headless counterpart of plumb_outline), which rescues a lot of overlap. But the build direction has several near-siblings: plumb_design, plumb_brand, plumb_studio, and the plumb_studio_start/kit/page trio all 'build from a brief into Figma,' and plumb_node/plumb_query/plumb_selection/plumb_outline are all extraction paths whose boundaries still require careful reading.
Everything is plumb_-prefixed snake_case, which is highly predictable, and variants are scoped sensibly (plumb_fig_outline, plumb_studio_kit). Minor deviation: some names are bare nouns (plumb_status, plumb_outline, plumb_node, plumb_tokens) while others are verb_noun (plumb_import_web, plumb_emit_react, plumb_scan_references, plumb_assign-style verbs). Readable but not a single uniform pattern.
28 tools is at the 'too many' end, and the breadth is partly real redundancy rather than necessity: plumb_studio duplicates the intent of plumb_studio_start/kit/page, and plumb_brand overlaps plumb_studio_start, so whole flows exist in two forms. The domain is genuinely large, but several tools could be consolidated behind variants instead of separate entries.
The read (outline, node, tokens, query, search, components, selection), file-based (.fig), write (design/brand/studio), and QA (verify, fit, review, audit, diff) directions are all covered, plus web import and React emit — a very full lifecycle. Gaps are acknowledged: a11y checks (heading order, alt text) aren't built, and there's no tool to edit/move/delete existing Figma nodes, so mutation of an existing design requires re-emit.