figma-flow
Related Servers
Alternatives to figma-flow
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants like Claude Desktop to interact directly with Figma, allowing natural language commands to create, modify, and analyze designs including shapes, text, components, and layouts in real-time.MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to interact with Figma designs, convert designs to code, extract variables, get screenshots, and more.1-
- AlicenseBqualityBmaintenanceEnables Claude to connect to Figma without a paid plan, offering auto-connect and 100+ tools for document manipulation, design system sync, and code-to-Figma conversion.100257 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude to read and manipulate Figma documents in real-time through 62 operations including creating shapes, modifying styles, managing components, and exporting assets via a WebSocket bridge to a Figma plugin.221 npm81MIT
- AlicenseCqualityDmaintenanceEnables Claude Desktop and other AI tools to interact directly with Figma, allowing for powerful AI-assisted design capabilities through natural language commands.92401 npm673MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to create and edit Figma designs in real time through MCP tools, allowing natural language commands for generating slides, charts, and other elements.949 npmMIT
TDQS
Scored across 5 tools
create_flowchart, draw_demo_flowchart, and clear_canvas are clearly distinct in purpose. The main overlap is between ping and get_status, which both serve as health/connectivity checks, though get_status specifically reports plugin connection state.
All names use snake_case consistently, which is good. However, the convention is not fully uniform: 'ping' is a bare verb, 'get_status' uses verb_noun, and the drawing tools mix 'draw_' and 'create_' as prefixes for similar operations.
Five tools is well-scoped for a lightweight Figma flowchart plugin: health checks, connection status, chart creation, demo creation, and canvas clearing. Each tool has a clear role and none feels redundant.
The surface covers creating and clearing flowcharts, plus setup checks, but lacks operations to list, update, or delete individual existing flowcharts. The only removal tool clears the entire canvas, which is a notable gap for repeated editing workflows.