Figma Edit MCP
Related Servers
Alternatives to Figma Edit MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to access Figma design context, generate code from frames, extract variables, components, and layout data, and create or modify Figma files directly from MCP clients.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI clients to read and modify the user's currently open Figma file by executing JavaScript in Figma's sandbox, all through a local bridge with status monitoring, node jumping, and automatic rollback on errors.1MIT
- 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-

Figma MCP Serverofficial
FlicenseNot gradedqualityBmaintenanceProvides Figma design context to AI agents, enabling code generation, design system integration, and canvas manipulation through MCP.2,022-- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create, modify, and manage Figma designs through natural language commands via a specialized MCP server and plugin bridge. It supports a wide range of operations including element creation, property modification, component management, and accessibility checks.3 npm106MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that connects AI clients to Figma, enabling real-time reading, creation, and modification of designs using natural language.MIT
TDQS
Scored across 45 tools
Each tool targets a distinct resource/action pair, and even the three fill-related setters (node_set_fill, node_apply_style, node_bind_variable) have explicit routing guidance in their descriptions. No two tools perform the same operation, so an agent can reliably select the correct one.
Tools consistently use a resource_verb pattern (e.g., page_, node_, create_, style_), but read operations use both 'info' and 'list' (page_info vs style_list), and write operations mix 'set', 'apply', 'bind', 'manage', and 'update'. This is mostly consistent but not fully uniform.
With 45 tools, the server far exceeds the typical well-scoped range. While the broad Figma domain justifies extensive coverage, the highly granular setters (fill, stroke, corner radius, effects, auto layout) could be consolidated, making the tool surface disproportionately large and harder to navigate.
The server provides comprehensive coverage of node, style, component, variable, annotation, and reaction operations, with read/update/delete for most resources. Minor gaps include no annotation deletion or page-level manipulation beyond listing, but these are workable and do not create dead ends.