op-product-design-mcp
Related Servers
Alternatives to op-product-design-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to build and edit a local-first design board of HTML screens, flows, components, design-system pages, and plan tables, then review it in a browser with undo/restore, rendering, and export tools.MIT
- AlicenseNot gradedqualityCmaintenanceGives AI assistants a fully offline toolchain for FlyThings OS human-machine interface development: converting HTML prototypes into JSON/FTU layouts, packaging and deploying firmware to devices, capturing real-device screenshots for pixel-diff acceptance, and generating i18n, tests, and bug reports. It also bundles a local vector-plus-BM25 knowledge base covering hardware models, UI control semantics, dependency manifests, and reusable components.MIT
- AlicenseAqualityAmaintenanceIt lets AI coding agents look up design tokens, component specifications, and prohibition rules on demand, then validate generated HTML or JSX with the same lint logic used by CI and editor hooks so violations are caught and corrected immediately. It also exposes the design constitution and rule sets as resources for reference during generation.6567 npm201MIT

livefolioofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, version, review, publish, and manage interactive HTML folios locally, with support for feedback collection and sharing via tunnels.2AGPL 3.0- AlicenseNot gradedqualityBmaintenanceEnables AI agents to write AI-generated designs into design-tool canvases (MasterGo, Penpot) as native editable layers, and to read canvas selections back out as HTML + Tailwind, design tokens, and SVG assets. Runs locally with progressive tool disclosure and structurally truncated results so large design files stay within an agent's context budget.Apache 2.0

WunderUI MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to build UI with a design system's tokens, component inventory and prop signatures, page templates, and starter snippets, while tracking free/pro availability and live-updating design data.1,151 npm1MIT
TDQS
Scored across 9 tools
Most tools have distinct roles: get_brief (mandatory preamble), get_bundled_css (style tokens), validate_prototype (read-only check), export_prototype (single-file output). However create_prototype overlaps with start_preview since it also launches preview and returns a URL, and create/update_prototype boundary is only clarified by the overwrite wording. Boundaries are mostly clear but one pair needs the description to disambiguate.
All nine tools follow a consistent snake_case verb_noun pattern (get_brief, create_prototype, update_prototype, get_prototype, start_preview, list_prototypes, validate_prototype, export_prototype) with only get_bundled_css deviating slightly in noun form. The convention is predictable and uniform.
Nine tools is well-scoped for a prototype authoring workflow, covering fetch/read/create/update/validate/preview/export/list with no redundant filler. Each tool earns its place in the lifecycle.
The surface covers the core lifecycle (read brief, get/read prototype, create, update, validate, preview, export, list) with no dead ends for the main flow. Minor gaps: no delete_prototype to remove stale drafts and no explicit preview-stop, but these are workable around.