A
licenseB
qualityNot graded
maintenanceEnables Cursor AI to communicate with Figma for reading designs and modifying them programmatically, allowing users to automate design tasks through natural language.
38
1,138 npm
1
-
Talk to Figma MCP
by yhc984
Related Servers
Alternatives to Talk to Figma MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Cursor AI to read and modify Figma designs via the Model Context Protocol, allowing programmatic control over documents, components, styles, and more.1,138 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants like Cursor to interact with Figma designs programmatically. Supports reading design information, modifying elements, creating components, managing text content, and automating design workflows through natural language commands.1,138 npmMIT
- AlicenseBqualityDmaintenanceAllows Cursor AI to communicate with Figma for reading designs and modifying them programmatically through a Model Context Protocol integration.381,138 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables coding agents like Cursor to access Figma design data, fetch layout and styling information, and implement designs in any framework.83,997 npmMIT
- FlicenseBqualityDmaintenanceEnables Cursor AI to read and modify Figma designs programmatically via the Model Context Protocol.381,138 npm3-
TDQS
B3.3/5.0
Scored across 40 tools
Disambiguation4/5
Most tools have distinct purposes, but there is some overlap between 'get_node_info', 'get_nodes_info', and 'read_my_design' which all retrieve node details, potentially causing confusion. Additionally, 'set_multiple_annotations' and 'set_annotation' serve similar functions with minor scaling differences. Overall, the set is well-differentiated with only a few ambiguous pairs.
Naming Consistency5/5
All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., 'create_frame', 'delete_node', 'get_styles'). The naming is highly predictable and uniform across all 40 tools, making it easy for agents to understand and use them.
Tool Count2/5
With 40 tools, this server feels overloaded for a Figma integration. Many tools could be consolidated (e.g., multiple 'set_' tools for styling or layout), leading to a bloated interface that may overwhelm agents. A more streamlined set of 15-25 tools would better suit the domain without sacrificing functionality.
Completeness5/5
The tool set provides comprehensive coverage for Figma operations, including CRUD for nodes (create, get, update, delete), styling, layout management, annotations, exports, and prototyping. There are no obvious gaps; agents can perform full design workflows from creation to export and collaboration.
Maintenance
ActivityInactive
ResponsivenessNo issues