A
licenseB
qualityD
maintenanceAn MCP server integration that enables Cursor AI to communicate with Figma, allowing users to read designs and modify them programmatically through natural language commands.
19
669 npm
7,050
MIT
Layerwright
by shayan-m81
Related Servers
Alternatives to Layerwright
- FlicenseAqualityDmaintenanceEnables interaction with Figma files through intelligent API access, providing navigation, asset extraction, and design token retrieval with 95% token-optimized compact tree output format.151-
Related Servers
- AlicenseCqualityDmaintenanceEnables Claude Desktop and other AI tools to interact directly with Figma, allowing for powerful AI-assisted design capabilities through natural language commands.92234 npm670MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to interact with Figma designs, convert designs to code, extract variables, get screenshots, and more.1-
- AlicenseBqualityBmaintenanceEnables Claude to connect to Figma without a paid plan, offering auto-connect and 100+ tools for document manipulation, design system sync, and code-to-Figma conversion.10034 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to interact directly with Figma Desktop for creating UI components, managing design tokens, and auditing files through natural language. It establishes a live connection between the AI and the Figma API via a local server and companion plugin.4,593 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants like Claude Desktop to interact directly with Figma, allowing natural language commands to create, modify, and analyze designs including shapes, text, components, and layouts in real-time.MIT
- FlicenseAqualityDmaintenanceEnables Claude AI to extract design information from Figma files and create or update designs via a Figma plugin, supporting both readonly and write modes.936-
TDQS
A3.5/5.0
Scored across 22 tools
Disambiguation4/5
Most tools target a distinct stage of the Figma workflow (status, scan, inspect, plan/preview/execute, verify, analyze/apply, edit, migrate). A few boundaries blur, notably figma_import_html vs import_html_to_plan and the all-in-one figma_edit overlapping with specialized ops like figma_apply_transformations and figma_migrate, but descriptions differentiate them well.
Naming Consistency4/5
Names are predominantly consistent snake_case with subsystem prefixes (figma_*, code_*, layerwright_*), which reads predictably. The outlier import_html_to_plan breaks the figma_ prefix used by its sibling figma_import_html, and a few tools are bare verbs (figma_inspect, figma_verify), a minor deviation.
Tool Count4/5
22 tools sits in the heavy range, but the scope (Figma bridge, design-system scan/foundations, plan preview/execute/verify, HTML import, code mapping) is genuinely broad and most tools earn their place. Slightly over-stuffed, with the two HTML-import tools and the mega figma_edit the main candidates for consolidation.
Completeness4/5
The surface covers a full design-to-code lifecycle: status/cleanup, DS scan and foundations, node inspection, plan preview/execute/verify, non-destructive analysis/apply, editing, migration, image export, selection, project memory, and code scan/mapping/verification. Gaps are minor, e.g. no explicit design-system element deletion or standalone code-generation output tool.
Maintenance
ActivityMaintained
ResponsivenessWithin a week