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
Cursor Talk to Figma MCP
by paragdesai1
Related Servers
Alternatives to Cursor 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-
- AlicenseBqualityDmaintenanceAllows Cursor AI to communicate with Figma for reading designs and modifying them programmatically through a Model Context Protocol integration.381,138 npm1MIT
- AlicenseNot gradedqualityBmaintenanceModel Context Protocol integration for the Figma API, enabling AI applications to access Figma files, components, and design tokens.MIT
- AlicenseBqualityDmaintenanceEnables seamless interaction with Figma via the Model Context Protocol, allowing LLM applications to access, manipulate, and track Figma files, components, and variables.22,347 npm150MIT
- 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
TDQS
B3.1/5.0
Scored across 33 tools
Disambiguation3/5
Most tools have distinct purposes, but some overlap exists. For example, 'get_selection' and 'read_my_design' both retrieve selection information, and 'get_node_info' vs 'get_nodes_info' are similar but for single vs multiple nodes. Descriptions help clarify, but an agent might occasionally misselect between closely related tools.
Naming Consistency5/5
Tool names follow a consistent snake_case verb_noun pattern throughout, such as 'create_frame', 'delete_node', and 'set_fill_color'. The naming is predictable and readable, with no deviations in style or convention across all 33 tools.
Tool Count2/5
With 33 tools, the count is too high for a typical MCP server, making it feel heavy and potentially overwhelming. While Figma is a complex domain, this many tools suggests fragmentation rather than a well-scoped set, which could hinder agent usability.
Completeness4/5
The tool set covers a wide range of Figma operations, including creation, deletion, modification, and querying of nodes, with good lifecycle coverage. Minor gaps exist, such as no explicit tool for updating node properties beyond specific setters or handling component overrides, but agents can likely work around these.
Maintenance
ActivityInactive
ResponsivenessNo issues