A side-by-side look at the Figma Flutter MCP and UI Design to Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figma Flutter MCP for architecture & design work as a local process; choose UI Design to Code for architecture & design as a local process. You can also run both side by side in one mcpServers block.
FIGMA_API_KEY.export_flutter_assets, export_svg_flutter_assets, analyze_figma_component.get_run_modes, create_design_run, ingest_image_source.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 64/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | FIGMA_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 244 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 13 | 14 |
| Full listing | View Figma Flutter MCP | View UI Design to Code |
export_flutter_assetsExport images from Figma nodes and set up Flutter assets directory with pubspec.yamlexport_svg_flutter_assetsExport SVG assets from Figma nodes. Detects SVG content by analyzing vector percentage - nodes with >30% vector content are considered SVG assets. Handles nested GROUP/FRAME structures with mixed content.analyze_figma_componentAnalyze a Figma component or component set to extract layout, styling, and structure information for Flutter widget creation. Use analyze_full_screen for complete screen layouts.list_component_variantsList all variants in a Figma component set to help with variant selectioninspect_component_structureGet a quick overview of component structure, children, and nested components. Use inspect_screen_structure for full screens.generate_flutter_implementationGenerate complete Flutter widget code using cached style definitionsstyle_library_statusGet comprehensive status report of the cached style libraryanalyze_full_screenAnalyze a complete Figma screen/frame to extract layout, sections, navigation, and structure information for Flutter screen implementationinspect_screen_structureGet a quick overview of screen structure, sections, and navigation elementsextract_theme_colorsExtract colors from a Figma theme frame containing color swatches with labelsinspect_theme_frameInspect the structure of a theme frame to understand its contents before extractionextract_theme_typographyExtract typography styles from a Figma theme frame containing text samples with different stylesget_run_modesReturns supported modes, target platforms, trigger examples, and the mode-selection prompt.create_design_runCreates the run directory and `artifact-run-manifest.json`.ingest_image_sourceRegisters a screenshot or image into:ingest_figma_sourceRegisters Figma MCP node JSON, an optional screenshot, or both.slice_image_assetsCrops bitmap/icon assets from a source image using a `layers.manifest.json` with `source_bbox` entries.build_reference_analysisRegisters model-generated Reference Image Analysis before Vision IR. This captures the original pixel size, root frame, semantic top-level groups, text/media/icon/material inventory, bottom navigation, strict extraction settings, high-risk zones, and the audit plan used for later decoding.build_semantic_irRegisters model-generated Platform-neutral Semantic UI IR.build_cross_platform_nodesRegisters Cross-platform Node Data.build_target_irRegisters target-platform layout IR for a selected target.run_codegenRecords implementation output and validation summary without enforcing visual review.run_codegen_with_auto_reviewRecords implementation output plus visual review evidence.validate_pipelineValidates an existing run by checking required artifacts and traceability links between vision, compression, semantic, cross-platform, and target planning artifacts.Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"mhmzdev-figma-flutter-mcp": {
"command": "npx",
"args": [
"-y",
"figma-flutter-mcp"
],
"env": {
"FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE"
}
}
}
}
{
"mcpServers": {
"ui-design-to-code": {
"command": "npx",
"args": [
"-y",
"ui-design-to-code-mcp@latest"
]
}
}
}