A
licenseNot graded
qualityB
maintenanceBridges AI assistants with Figma for design system extraction, bidirectional token sync, visual debugging, and design creation.
69 npm
1
MIT
figma-spec-mcp
by zaferdace
Related Servers
Alternatives to figma-spec-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceConverts Figma designs into structured code context with token-aware styling, enabling AI agents to generate production-level frontend code.16 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables seamless integration with Figma API for extracting design tokens, generating production-ready code in multiple frameworks, capturing screenshots, and managing design assets directly from Figma.5MIT
- AlicenseNot gradedqualityDmaintenanceConnects Figma designs to AI agents, enabling extraction of production-ready code, assets, and design tokens through natural language descriptions. Supports React, Vue, CSS, and Tailwind with real-time design system analysis.60,727 npm40MIT
- AlicenseAqualityDmaintenanceConverts Figma designs into production-ready React components with design token extraction, widget registry integration, and micro-frontend module generation.328 npm1MIT
- AlicenseNot gradedqualityDmaintenanceExports Figma designs as ready-to-use HTML/CSS and validates pixel-perfect accuracy with image comparison and visual regression testing.4 npmMIT
TDQS
A3.8/5.0
Scored across 19 tools
Disambiguation5/5
Each tool targets a distinct aspect of the Figma-to-code workflow (accessibility auditing, layout inspection, token extraction, flow extraction, component resolution, framework-specific mapping, etc.). Even the five map_to_* tools are clearly separated by target framework, and the extraction tools each focus on a different data type (tokens, flows, variants, states).
Naming Consistency4/5
Names follow a consistent snake_case convention and most use a verb_noun structure (audit_accessibility, extract_variants, resolve_components). A few conversion tools use a 'to' pattern (map_to_react, bridge_to_codebase) which is coherent, but flow_to_test_cases deviates by starting with a noun instead of a verb.
Tool Count4/5
With 19 tools, the count is on the heavier side but well-justified for a comprehensive Figma design-to-development server. Each tool serves a distinct purpose in the workflow, and the scope is broad enough to warrant the number without feeling bloated.
Completeness5/5
The tool surface covers the full read-only design-to-code pipeline: extraction, analysis, mapping to multiple frameworks, asset export, version diffing, component resolution, test case generation, and handoff readiness checks. There are no obvious missing operations for its stated purpose, and the addition of bridge_to_codebase and simplify_context further fills collaboration and context-efficiency gaps.
Maintenance
ActivityInactive
ResponsivenessNo issues