Figma MCP Server
Related Servers
Alternatives to Figma MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityNot gradedmaintenanceA Model Context Protocol server that provides access to Figma API functionality, allowing AI assistants like Claude to interact with Figma files, comments, components, and team resources.18857 npm4-
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server that bridges design and development by giving AI assistants complete access to Figma for extraction, creation, debugging, and bidirectional token sync.49,681 npm2,368MIT
- 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.2,347 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA server implementation that enables interaction with Figma API through Model Context Protocol (MCP), supporting plugin and widget development with WebSocket communication capabilities.2,347 npm3MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI agents to programmatically create, modify, and manage Figma documents via a WebSocket bridge and Figma plugin.116MIT
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol server that integrates Figma design files with AI coding tools like Cursor, Windsurf, and Cline, allowing AI tools to access and understand Figma design data for generating more accurate code.171 npm31MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: adding files, posting comments, reading comments, replying to comments, and viewing nodes. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent verb_noun pattern (e.g., add_figma_file, post_comment, read_comments, reply_to_comment, view_node). This uniformity enhances readability and predictability for agents.
With 5 tools, the server is well-scoped for its purpose of managing Figma files and comments. Each tool serves a specific, necessary function without bloat or redundancy.
The toolset covers core operations for file management and comment interactions, but lacks CRUD coverage for files (e.g., no update or delete file tools). However, agents can likely work around this minor gap for basic workflows.