{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"github_mcp-matthewdailey-figma-mcp","slug":"mcp-matthewdailey-figma-mcp","name":"figma-mcp","type":"mcp","url":"https://github.com/MatthewDailey/figma-mcp","page_url":"https://unfragile.ai/mcp-matthewdailey-figma-mcp","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"github_mcp-matthewdailey-figma-mcp__cap_0","uri":"capability://tool.use.integration.figma.document.tree.traversal.and.introspection","name":"figma document tree traversal and introspection","description":"Exposes Figma's REST API document hierarchy through MCP tools, enabling programmatic access to file structure, layers, components, and design tokens. Works by wrapping Figma's GET /v1/files/{file_id} endpoint and parsing the hierarchical JSON response into queryable node structures with metadata about frame bounds, fill colors, typography, and component references.","intents":["Query a Figma file's layer structure and component hierarchy without opening the UI","Extract design metadata (colors, typography, spacing) from a design file programmatically","Identify component instances and their overrides across a design system","Analyze frame nesting depth and layer organization for design audit purposes"],"best_for":["Design system maintainers automating design-to-code workflows","AI agents that need to understand design structure before generating code","Teams building design-aware documentation generators"],"limitations":["Read-only access to document structure — cannot modify designs through this capability","Requires full file read permission; cannot scope to specific pages or components","Large files (1000+ layers) may incur latency from Figma API response times","No real-time sync — returns snapshot at query time, not live updates"],"requires":["Figma API token with read access to target files","File ID of the Figma document to query","Network connectivity to Figma's REST API endpoints"],"input_types":["file_id (string)","optional: page_id (string) for scoped queries"],"output_types":["JSON tree structure with node metadata","Flattened layer list with hierarchy markers","Component reference map"],"categories":["tool-use-integration","design-system-tooling"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-matthewdailey-figma-mcp__cap_1","uri":"capability://data.processing.analysis.component.instance.resolution.and.override.tracking","name":"component instance resolution and override tracking","description":"Resolves component instances to their main component definitions and tracks applied overrides (property changes, nested swaps). Implemented by following Figma's componentId references through the document tree and comparing instance properties against the main component's defaults to identify which properties have been overridden.","intents":["Find all instances of a specific component and their override patterns","Detect inconsistent overrides that violate design system rules","Generate code that respects component override semantics","Audit component usage across a design file"],"best_for":["Design system teams enforcing component consistency","Code generators that need to preserve design intent through overrides","Design QA workflows checking for misused components"],"limitations":["Cannot track override history or changes over time","Nested component overrides require recursive traversal which adds latency","Does not validate override combinations against design system rules","Main component must be in the same file or accessible shared library"],"requires":["Figma API token with access to component libraries","Component IDs or names to track","File containing both main components and instances"],"input_types":["component_id (string)","file_id (string)"],"output_types":["Array of instance objects with override deltas","Mapping of instance IDs to override properties","Component usage statistics"],"categories":["data-processing-analysis","design-system-tooling"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-matthewdailey-figma-mcp__cap_10","uri":"capability://data.processing.analysis.constraint.and.responsive.behavior.extraction","name":"constraint and responsive behavior extraction","description":"Extracts constraint rules (fixed/flexible width/height, left/right/center alignment) and responsive behavior metadata from Figma elements. Parses constraint properties to understand how elements resize relative to their parent, enabling responsive layout code generation.","intents":["Generate responsive CSS that respects Figma constraint rules","Document responsive behavior for developers","Validate that designs have proper constraints for responsiveness","Create layout specifications with constraint information"],"best_for":["Design-to-code tools that need to preserve responsive intent","Teams documenting responsive design specifications","Responsive design validation tools"],"limitations":["Constraint rules are extracted but not evaluated (no layout simulation)","Does not capture CSS media queries or breakpoint logic","Constraints are relative to parent — requires full hierarchy context","No information about overflow behavior or scroll regions"],"requires":["Figma file with constrained elements","Figma API token with read access"],"input_types":["file_id (string)","optional: node_id (string) for scoped extraction"],"output_types":["Array of constraint definitions per element","Constraint hierarchy map","Responsive behavior summary"],"categories":["data-processing-analysis","design-system-tooling"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-matthewdailey-figma-mcp__cap_11","uri":"capability://data.processing.analysis.shadow.and.effect.property.extraction","name":"shadow and effect property extraction","description":"Extracts shadow, blur, and other visual effects from Figma elements, normalizing them to CSS or design token format. Works by parsing Figma's effects array (shadows, blurs, background blurs) and converting to standard CSS syntax or design token representations.","intents":["Generate CSS box-shadow and filter properties from Figma designs","Create effect design tokens from Figma styles","Document visual effects for developers","Audit effect usage across a design file"],"best_for":["Design-to-code tools that need to preserve visual effects","Design system teams documenting effect tokens","Teams creating comprehensive design specifications"],"limitations":["Complex effects with multiple layers may not map cleanly to CSS","Blur effects have limited CSS support (background-blur is not standard)","Effect stacking order is preserved but may not render identically in CSS","No information about effect animation or transitions"],"requires":["Figma file with elements that have effects","Figma API token with read access"],"input_types":["file_id (string)","optional: node_id (string) for scoped extraction","optional: output_format (string: 'css', 'token')"],"output_types":["Array of effect definitions with CSS equivalents","Effect token definitions","Effect usage report"],"categories":["data-processing-analysis","design-system-tooling"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-matthewdailey-figma-mcp__cap_2","uri":"capability://data.processing.analysis.design.token.extraction.and.structured.export","name":"design token extraction and structured export","description":"Extracts design tokens (colors, typography, spacing, shadows) from Figma styles and component properties, normalizing them into structured JSON or CSS variable format. Works by parsing Figma's style definitions (fill colors, text styles, effects) and mapping them to token categories, then generating standardized output formats compatible with design token standards (Design Tokens Community Group format).","intents":["Export color palette from a Figma file as CSS variables or JSON","Generate typography scale definitions from Figma text styles","Create spacing/sizing token files from component dimensions","Sync design tokens to code without manual transcription"],"best_for":["Design system teams automating token sync from Figma to code","Frontend teams building token-driven component libraries","Organizations standardizing design-to-dev handoff workflows"],"limitations":["Requires styles to be properly organized in Figma (flat naming conventions work best)","Does not infer semantic token relationships (e.g., 'primary' vs 'secondary') — requires explicit naming","Complex nested styles may not map cleanly to standard token formats","No validation that exported tokens are actually used in components"],"requires":["Figma file with defined styles (colors, typography, effects)","Figma API token with read access","Target output format specification (CSS, JSON, SCSS, etc.)"],"input_types":["file_id (string)","style_type filter (optional: 'color', 'typography', 'effect')","output_format (string: 'css', 'json', 'scss')"],"output_types":["CSS custom properties file","JSON token object","SCSS variable file","Design Tokens Community Group format"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-matthewdailey-figma-mcp__cap_3","uri":"capability://tool.use.integration.mcp.tool.registration.and.schema.generation","name":"mcp tool registration and schema generation","description":"Registers Figma API operations as MCP tools with auto-generated JSON schemas, enabling LLM agents to discover and call Figma capabilities through a standardized interface. Implemented by wrapping Figma REST endpoints with MCP's tool schema format, generating input/output schemas from Figma API specifications, and handling authentication transparently through MCP's credential management.","intents":["Enable Claude or other LLM agents to query Figma files without custom code","Expose Figma capabilities to multi-tool agent workflows","Allow non-technical users to interact with Figma data through natural language","Integrate Figma operations into broader design automation pipelines"],"best_for":["AI agent developers building design-aware automation","Teams using Claude or other LLM agents for design workflows","Organizations building no-code design automation interfaces"],"limitations":["Schema generation is static — does not adapt to Figma API changes automatically","LLM agents may misinterpret complex nested schemas or make invalid API calls","No built-in rate limiting or quota management for Figma API calls","Requires careful prompt engineering to guide agents toward correct tool usage"],"requires":["MCP server runtime (Node.js 18+)","Figma API token configured as environment variable","MCP client that supports tool discovery (Claude Desktop, custom agents)"],"input_types":["MCP tool invocation with JSON parameters"],"output_types":["JSON response from Figma API","Structured error messages with remediation hints"],"categories":["tool-use-integration","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-matthewdailey-figma-mcp__cap_4","uri":"capability://search.retrieval.figma.file.and.page.enumeration.with.metadata","name":"figma file and page enumeration with metadata","description":"Lists accessible Figma files and pages with metadata (name, last modified, owner, thumbnail URL) by calling Figma's REST endpoints for team/project resources. Returns structured data about available design files, enabling agents or applications to discover and select files without hardcoding file IDs.","intents":["Discover available Figma files in a team or project","Display file list with metadata for user selection","Audit which files exist and who owns them","Build dynamic workflows that adapt to available design files"],"best_for":["Multi-file design workflows where file selection is dynamic","Design audit and governance tools","Agents that need to discover available design assets"],"limitations":["Requires team-level API token; cannot enumerate files from other teams","Pagination required for teams with 100+ files","Metadata is limited to what Figma's REST API exposes (no custom properties)","File list is static snapshot — does not reflect real-time file creation/deletion"],"requires":["Figma API token with team access","Team ID or project ID to enumerate"],"input_types":["team_id (string)","optional: project_id (string) for scoped enumeration"],"output_types":["Array of file objects with metadata","Pagination tokens for large result sets"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-matthewdailey-figma-mcp__cap_5","uri":"capability://data.processing.analysis.frame.and.artboard.boundary.extraction","name":"frame and artboard boundary extraction","description":"Extracts bounding box coordinates, dimensions, and layout properties (auto-layout, constraints) for frames and artboards in a Figma file. Implemented by parsing the node tree and extracting x, y, width, height properties along with layout metadata, enabling spatial analysis and layout-aware code generation.","intents":["Generate responsive layout code that respects Figma frame dimensions","Analyze spatial relationships between design elements","Create layout specifications for developers","Validate that designs fit within target screen sizes"],"best_for":["Design-to-code tools that need layout information","Responsive design validators","Teams documenting layout specifications"],"limitations":["Does not capture visual rendering (colors, shadows, images) — only geometry","Constraints and auto-layout rules are extracted but not evaluated (no layout simulation)","Rotated or skewed frames require additional transformation calculations","No information about overflow behavior or scroll regions"],"requires":["Figma file with frames/artboards","Figma API token with read access"],"input_types":["file_id (string)","optional: frame_id (string) for scoped extraction"],"output_types":["Array of frame objects with bounding box and layout properties","Spatial relationship map"],"categories":["data-processing-analysis","design-system-tooling"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-matthewdailey-figma-mcp__cap_6","uri":"capability://tool.use.integration.image.and.asset.url.resolution","name":"image and asset url resolution","description":"Resolves image nodes and assets in Figma to their download URLs, enabling external tools to fetch design assets. Works by extracting image node IDs and calling Figma's image export endpoint to generate temporary signed URLs for asset retrieval.","intents":["Download design assets (images, icons) from Figma for use in code","Build asset pipelines that sync Figma images to CDN or asset management systems","Generate image references in code from Figma designs","Extract icon sets or illustration libraries from Figma"],"best_for":["Design-to-code pipelines that need to reference design assets","Asset management and DAM integration workflows","Icon library extraction and distribution"],"limitations":["URLs are temporary and expire after a short period (typically 24 hours)","Requires separate download step — does not directly embed images","Export format is limited to what Figma supports (PNG, SVG, PDF)","Large batch exports may hit Figma API rate limits"],"requires":["Figma API token with read access","File ID and image node IDs","Network access to download generated URLs"],"input_types":["file_id (string)","node_id (string) or array of node_ids","optional: format (string: 'png', 'svg', 'pdf')","optional: scale (number: 0.5 to 4)"],"output_types":["Array of signed download URLs","Image metadata (dimensions, format)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-matthewdailey-figma-mcp__cap_7","uri":"capability://data.processing.analysis.text.content.and.typography.extraction","name":"text content and typography extraction","description":"Extracts text content, font families, sizes, weights, and line heights from text nodes in Figma designs. Implemented by traversing text nodes and parsing their style properties (fontSize, fontFamily, fontWeight, lineHeight, letterSpacing) into structured format, enabling typography-aware code generation and content extraction.","intents":["Extract copy and content from designs for CMS or documentation","Generate typography CSS from Figma text styles","Audit font usage across a design file","Create accessible HTML with proper semantic markup and typography"],"best_for":["Content-driven design workflows where copy needs extraction","Typography system documentation and validation","Accessibility-focused design-to-code tools"],"limitations":["Does not extract text styling applied at character level (only paragraph-level styles)","Font files are not included — only font names (requires separate font loading)","Does not capture text transformations (uppercase, lowercase) applied via CSS","Multi-language text requires separate language detection"],"requires":["Figma file with text nodes","Figma API token with read access"],"input_types":["file_id (string)","optional: text_node_id (string) for scoped extraction"],"output_types":["Array of text objects with content and typography properties","Typography scale summary","Font usage report"],"categories":["data-processing-analysis","text-generation-language"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-matthewdailey-figma-mcp__cap_8","uri":"capability://data.processing.analysis.color.and.fill.property.extraction","name":"color and fill property extraction","description":"Extracts fill colors, gradients, and opacity values from design elements, normalizing them to standard color formats (hex, RGB, HSL). Works by parsing Figma's fill array and converting color values to multiple formats for compatibility with different code targets (CSS, Tailwind, design tokens).","intents":["Extract color palette from a design for code generation","Generate Tailwind color configuration from Figma designs","Audit color usage and identify palette inconsistencies","Create color documentation from designs"],"best_for":["Design-to-code tools that need color information","Design system teams documenting color palettes","Accessibility tools validating color contrast"],"limitations":["Does not evaluate color contrast or accessibility compliance","Gradient extraction is limited to linear/radial gradients (no mesh gradients)","Color space conversions may have rounding errors in edge cases","Does not track color semantics (e.g., which colors are 'primary' vs 'secondary')"],"requires":["Figma file with colored elements","Figma API token with read access"],"input_types":["file_id (string)","optional: node_id (string) for scoped extraction","optional: output_format (string: 'hex', 'rgb', 'hsl', 'tailwind')"],"output_types":["Array of color objects with multiple format representations","Color usage frequency map","Gradient definitions"],"categories":["data-processing-analysis","design-system-tooling"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-matthewdailey-figma-mcp__cap_9","uri":"capability://data.processing.analysis.variant.and.variant.group.resolution","name":"variant and variant group resolution","description":"Identifies component variants and their property combinations, mapping variant properties to their values. Implemented by parsing Figma's variant metadata (variant properties like 'size', 'state', 'color') and resolving variant instances to their property combinations, enabling variant-aware code generation.","intents":["Generate component code that supports all variant combinations","Document component variants and their properties","Validate that all variant combinations are designed","Create variant selection logic for component libraries"],"best_for":["Component library teams with complex variant systems","Design-to-code tools that need to generate variant-aware components","Teams documenting component APIs"],"limitations":["Does not validate that all variant combinations are visually distinct","Variant property values are limited to what's defined in Figma (no dynamic values)","Complex nested variants may be difficult to traverse","No information about variant precedence or default values"],"requires":["Figma file with component variants","Figma API token with read access"],"input_types":["file_id (string)","component_id (string)"],"output_types":["Array of variant property definitions","Mapping of variant instances to property combinations","Variant matrix (all possible combinations)"],"categories":["data-processing-analysis","design-system-tooling"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":32,"verified":false,"data_access_risk":"high","permissions":["Figma API token with read access to target files","File ID of the Figma document to query","Network connectivity to Figma's REST API endpoints","Figma API token with access to component libraries","Component IDs or names to track","File containing both main components and instances","Figma file with constrained elements","Figma API token with read access","Figma file with elements that have effects","Figma file with defined styles (colors, typography, effects)"],"failure_modes":["Read-only access to document structure — cannot modify designs through this capability","Requires full file read permission; cannot scope to specific pages or components","Large files (1000+ layers) may incur latency from Figma API response times","No real-time sync — returns snapshot at query time, not live updates","Cannot track override history or changes over time","Nested component overrides require recursive traversal which adds latency","Does not validate override combinations against design system rules","Main component must be in the same file or accessible shared library","Constraint rules are extracted but not evaluated (no layout simulation)","Does not capture CSS media queries or breakpoint logic","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.23810648793701106,"quality":0.34,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:22.065Z","last_scraped_at":"2026-05-03T14:23:38.364Z","last_commit":"2025-05-29T22:16:06Z"},"community":{"stars":211,"forks":10,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=mcp-matthewdailey-figma-mcp","compare_url":"https://unfragile.ai/compare?artifact=mcp-matthewdailey-figma-mcp"}},"signature":"ptJl9cKDvFdmcAvkSg7Bul7SSWk+87j+6CS2EWBGqZvTpYNLRc5m4r1drmX+sqo2Lb05+WkT3trneXu5Xx7CDw==","signedAt":"2026-06-22T02:43:08.413Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/mcp-matthewdailey-figma-mcp","artifact":"https://unfragile.ai/mcp-matthewdailey-figma-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=mcp-matthewdailey-figma-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}