protoflow
Related Servers
Alternatives to protoflow
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to build and edit app-screen mockups and clickable prototypes by reading and writing structured scene models, including screen creation, node manipulation, and branching from code-based screens.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create and modify native Figma canvas designs through a companion desktop plugin, generating AutoLayout UI trees, UX state matrices, and interactive component variants while auditing cognitive UX heuristics and user journeys.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to read and modify Figma designs programmatically, supporting design analysis, element creation, text replacement, annotations, auto-layout configuration, and prototype visualization through natural language commands.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI to create interactive HTML-based software prototypes with navigation, markers, and annotations. Provides a complete prototyping environment without requiring tools like Figma or Axure.4-
- AlicenseBqualityBmaintenanceEnables AI assistants to read and write Figma designs, manage design tokens and variables, create components and FigJam boards, and run accessibility and design-code parity checks through a bidirectional Figma integration.1309,800 npmMIT
- AlicenseBqualityAmaintenanceEnables AI-driven UI/UX design and prototyping in Figma by letting agents generate AutoLayout screens, modify canvas elements, and wire interactive prototype flows through natural language.47MIT
TDQS
Scored across 22 tools
Most tools are clearly distinct, but render_preview and render_canvas are near-identical in behavior (both return the whole-canvas URL), and the generic `delete` tool is ambiguous without a resource prefix. This creates real misselection risk for agents.
The vast majority follow verb_noun (upsert_page, list_projects, create_doc, export_canvas), but `delete` and `chain_status` break the pattern. The inconsistent outliers are minor, so the set is still predictable overall.
22 tools falls into the heavy range (16–25) and the surfaced redundancy between render_preview and render_canvas could be trimmed. However, the breadth is mostly justified by the project/page/artboard/docs workflow.
Core lifecycle coverage is strong: projects can be listed/get/created/imported, pages/artboards can be upserted/deleted/reordered, source and annotations are writable, and docs can be built and published. Minor gaps remain: no dedicated get_source or get_doc tool (relying on file tools), and no project deletion or doc read utility.