F
licenseB
qualityD
maintenanceEnables AI assistants to interact with Figma files through the ModelContextProtocol, allowing viewing, commenting, and analyzing Figma designs directly in chat interfaces.
5
1,330 npm
213
-
Conduit
Related Servers
Alternatives to Conduit
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Python implementation of the Model Context Protocol server that enables AI assistants to interact with Figma through WebSocket connections, allowing them to read, analyze, and export design data.21-
- AlicenseNot gradedqualityDmaintenanceA server implementation that enables interaction with Figma API through Model Context Protocol (MCP), supporting plugin and widget development with WebSocket communication capabilities.1,620 npm3MIT
- AlicenseAqualityDmaintenanceAllow your AI coding agents to access Figma files & prototypes directly. You can DM me for any issues / improvements: https://x.com/jasonzhou1993 1. Access all figma pages 2. Access all figma components 3. Access figma prototype flows5327 PyPI67MIT
- FlicenseBqualityDmaintenanceEnables Cursor AI to interact with Figma designs, allowing users to read design information and programmatically modify elements through natural language commands.40707 npm3-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects AI tools and LLMs to Figma designs, enabling them to extract design data, analyze design systems, and generate development documentation.1,620 npm2MIT
TDQS
C2.8/5.0
Scored across 72 tools
Disambiguation3/5
Tools are generally distinct by resource and action (e.g., create_rectangle vs. resize_node), but there is significant overlap in style-setting tools (e.g., set_effect, set_gradient, apply_effect_style) and redundant getters (e.g., get_node_info, get_node_style, get_fill_and_stroke). This overlap could confuse agents about which tool to use for specific styling or info retrieval tasks.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern (e.g., create_rectangle, delete_node, get_document_info), with clear action prefixes. However, there are minor deviations like 'boolean' (noun instead of verb_noun) and 'join' (single verb without noun), slightly disrupting the pattern.
Tool Count2/5
With 72 tools, this server is extremely large for a Figma automation domain. While Figma has many features, this count feels excessive and overwhelming, likely leading to confusion and inefficiency for agents. A more focused set of 20-30 tools would be more manageable and appropriate.
Completeness5/5
The toolset comprehensively covers Figma operations, including creation (e.g., create_frame, create_component_instance), modification (e.g., resize_node, set_text_style), retrieval (e.g., get_node_info, get_svg_vector), deletion (e.g., delete_node), and advanced features like variables and events. There are no obvious gaps for core Figma workflows.