Talk to Figma MCP
Related Servers
Alternatives to Talk to Figma MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides write access to Figma through the Plugin API, enabling AI agents to create, modify, and manage Figma designs programmatically.23-

desrid-html-to-figmaofficial
AlicenseNot gradedqualityBmaintenanceThis MCP server lets AI agents connect to Figma to read, analyze, create, and modify designs, including elements, styles, assets, and code generation. It works with free Figma accounts and supports parallel multi-agent use across MCP-compatible clients.MIT- AlicenseNot gradedqualityAmaintenanceAn MCP server that enables AI tools to read and write Figma designs via a plugin bridge, bypassing the Figma REST API and rate limits.49MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects AI clients to Figma, enabling real-time reading, creation, and modification of designs using natural language.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI coding agents access to Figma design data, enabling pixel-perfect implementation of designs through structured data extraction, image downloads, and design token retrieval.27 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn open-source MCP server that gives AI assistants full read-write access to Figma, enabling creation, editing, and deletion of designs directly without plugins or API keys.39 npm10MIT
TDQS
Scored across 41 tools
Several tools have overlapping purposes: get_selection and read_my_design both return selection details; get_document_info, get_node_info, and get_nodes_info all fetch node/document information. This creates confusion about which tool to select for a given task.
Tool names overwhelmingly follow a verb_noun snake_case pattern (e.g., create_rectangle, set_fill_color, delete_node). Minor deviations like read_my_design and the singular/plural variation between set_annotation and set_multiple_annotations are slight but do not undermine the overall consistency.
With 41 tools, the server feels over-scoped for a design tool. While it offers a broad range of operations, the high count increases cognitive load and overlaps, making it difficult for an agent to efficiently choose the right tool. 25+ tools is beyond the comfortable range.
The tool set covers most core Figma workflows: node creation/deletion, editing properties, annotations, components, layout, and connections. Minor gaps exist (e.g., grouping, ungrouping, or advanced vector operations), but agents can accomplish typical design tasks without fundamental dead ends.