A
licenseNot graded
qualityD
maintenanceEnables Cursor AI to read and modify Figma designs via the Model Context Protocol, allowing programmatic control over documents, components, styles, and more.
1,138 npm
MIT
Talk to Figma MCP
by pipethedev
Related Servers
Alternatives to Talk to Figma MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables Cursor AI to read and modify Figma designs programmatically via the Model Context Protocol.381,138 npm3-
- AlicenseNot gradedqualityBmaintenanceEnables Cursor to access Figma files through the Model Context Protocol, enhancing its ability to accurately interpret and utilize design data for code generation.83,997 npm15,914MIT
- FlicenseBqualityDmaintenanceEnables Cursor AI to interact with Figma designs, allowing users to read design information and programmatically modify elements through natural language commands.401,138 npm3-
- AlicenseBqualityNot gradedmaintenanceEnables Cursor AI to communicate with Figma for reading designs and modifying them programmatically, allowing users to automate design tasks through natural language.381,138 npm1-
- AlicenseBqualityDmaintenanceImplements a Model Context Protocol integration between Cursor AI and Figma, allowing Cursor to programmatically read and modify Figma designs.331,138 npmMIT
TDQS
B3/5.0
Scored across 38 tools
Disambiguation3/5
Most tools have distinct purposes, but some overlap exists, such as 'get_node_info' and 'read_my_design' (both retrieve node details), and 'delete_node' and 'delete_multiple_nodes' (similar deletion functions). The descriptions help clarify differences, but agents might occasionally misselect between closely related tools.
Naming Consistency4/5
The tool names follow a consistent verb_noun pattern throughout, using snake_case uniformly, which aids readability. Minor deviations include 'read_my_design' (which uses 'my' instead of a direct verb_noun) and 'join_channel' (which is less descriptive of the domain), but overall the naming is predictable.
Tool Count2/5
With 38 tools, the count is excessive for a Figma interaction server, making it heavy and potentially overwhelming for agents. While Figma has a broad API, many tools could be consolidated (e.g., multiple set_* tools for styling), indicating poor scoping and an unnecessarily large surface.
Completeness5/5
The tool set provides comprehensive coverage for Figma operations, including CRUD for nodes (create, get, update, delete), styling (colors, layout, annotations), export, and component management. No obvious gaps exist; agents can perform full design workflows without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues