figma-mcp
Related Servers
Alternatives to figma-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, analyze, and modify Figma designs, including bulk style updates, accessibility audits, comment triage, and code generation from designs.243 npmMIT
- FlicenseAqualityDmaintenanceEnables AI agents to interact with Figma to create, read, and manage designs using the Figma REST API and a dedicated plugin. It supports advanced features like UI generation from text, webpage reconstruction in Figma, and design token synchronization with codebases.20-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to read and modify Figma designs programmatically, supporting design analysis, element creation, text replacement, annotations, auto-layout configuration, and prototype visualization through natural language commands.977 npmMIT
- AlicenseBqualityCmaintenanceEnables AI agents to directly control Figma Desktop via MCP, supporting UI creation, editing, prototyping, and variable management with over 60 tools.651,129 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to extract design systems, analyze components, and maintain design-code consistency from Figma files, providing intelligent component analysis and accessibility compliance.81 npm29MIT
- 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.-
TDQS
Scored across 47 tools
Several tools overlap heavily: ping_figma vs get_figma_status both check companion-plugin connectivity, and validate_user_journey, lint_design_compliance, audit_ux_heuristics, and lint_ux_microcopy all perform design/UX audits with subtle boundaries. Creation/planning tools (generate_ui_tree, plan_screen_architecture, create_frame) and retrieval tools (get_document_info, get_design_context, inspect_node, rest_get_file) also blur together, making misselection likely.
Nearly all tools follow a verb_noun snake_case pattern, with a clear rest_ prefix grouping cloud/REST operations. Minor deviations in verb choice (create vs generate vs plan vs audit vs lint) but the convention is predictable and readable throughout.
47 tools is heavy for a Figma companion server, and the surface includes many overlapping audit, retrieval, and creation paths that could be consolidated. The breadth is partly justified by canvas editing plus REST access, but the count clearly exceeds a well-scoped set.
Coverage is broad: create/update/delete nodes, text, frames, components, prototype wiring, design tokens, inspection, export, and cloud REST access including comments and variables. Minor gaps exist (e.g., no page deletion, no dedicated component-update or prototype-removal tool), but core workflows are well supported.