F
licenseB
qualityD
maintenanceEnables Cursor AI to interact with Figma designs, allowing users to read design information and programmatically modify elements through natural language commands.
40
1,138 npm
3
-
Cursor Talk to Figma MCP
by andreycretsu
Related Servers
Alternatives to Cursor Talk to Figma MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAllows Cursor AI to communicate with Figma for reading designs and modifying them programmatically through a Model Context Protocol integration.381,138 npm1MIT
- AlicenseBqualityDmaintenanceAn MCP server integration that enables Cursor AI to communicate with Figma, allowing users to read designs and modify them programmatically through natural language commands.191,138 npm7,039MIT
- AlicenseBqualityDmaintenanceImplements a Model Context Protocol integration between Cursor AI and Figma, allowing Cursor to programmatically read and modify Figma designs.331,138 npmMIT
- -licenseBqualityNot gradedmaintenanceEnables users to control the cursor in Figma through verbal commands using an agentic AI agent, streamlining the design process with a new interaction method.191,138 npm1-
- AlicenseNot gradedqualityDmaintenanceGives AI-powered coding tools like Cursor, Windsurf, and Cline access to Figma design files, enabling more accurate code generation directly from Figma designs.83,997 npmMIT
TDQS
B3.2/5.0
Scored across 38 tools
Disambiguation3/5
Most tools have distinct purposes, but there is some overlap and ambiguity. For example, 'get_selection' and 'read_my_design' both retrieve selection information, and 'get_node_info' vs 'get_nodes_info' differ only in singular/plural. However, descriptions clarify differences, and tools generally target specific actions like creation, deletion, or styling.
Naming Consistency4/5
Naming is mostly consistent with a verb_noun pattern (e.g., create_frame, delete_node, set_fill_color), but there are minor deviations like 'read_my_design' and 'join_channel' that break the pattern. Overall, the naming is predictable and readable, with only a few tools not following the dominant convention.
Tool Count3/5
With 38 tools, the count is borderline high for a Figma integration, feeling heavy and potentially overwhelming. While Figma is a complex domain, many tools could be consolidated (e.g., multiple 'set_' tools for styling). The scope is broad, but the number risks confusion and inefficiency for agents.
Completeness5/5
The tool set provides comprehensive coverage for interacting with Figma, including CRUD operations (create, get, update, delete), styling, layout management, annotations, and prototyping. There are no obvious gaps; tools cover nodes, components, text, images, connections, and document info, enabling full agent workflows without dead ends.