{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-iflow-mcpfigma-mcp","slug":"npm-iflow-mcpfigma-mcp","name":"@iflow-mcp/figma-mcp","type":"mcp","url":"https://www.npmjs.com/package/@iflow-mcp/figma-mcp","page_url":"https://unfragile.ai/npm-iflow-mcpfigma-mcp","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-iflow-mcpfigma-mcp__cap_0","uri":"capability://tool.use.integration.figma.document.introspection.via.mcp.protocol","name":"figma document introspection via mcp protocol","description":"Exposes Figma API endpoints as MCP tools, allowing LLM agents to query document structure, layers, components, and metadata through a standardized protocol interface. Implements MCP server specification to translate Figma REST API calls into tool definitions that language models can invoke, enabling agents to understand design file hierarchies without direct API knowledge.","intents":["Query Figma document structure and layer hierarchy programmatically","Retrieve component definitions and design system metadata from Figma files","Inspect design properties (colors, typography, spacing) for automation workflows","Enable LLM agents to reason about design files as part of multi-step workflows"],"best_for":["AI agents and LLM applications that need to read Figma design data","Design automation platforms integrating Figma as a data source","Teams building AI-assisted design-to-code pipelines"],"limitations":["Read-only introspection — no capability to modify or write changes back to Figma documents","Requires valid Figma API token with appropriate file access permissions","MCP protocol overhead adds latency compared to direct REST API calls","Limited to Figma API rate limits (120 requests per minute for standard tier)"],"requires":["Figma API token (personal access token or OAuth)","MCP client implementation (Claude Desktop, custom MCP host, or compatible LLM framework)","Node.js 16+ runtime environment","Network access to Figma API endpoints"],"input_types":["Figma file ID (string)","Node IDs for specific layers/components (string)","Query parameters for filtering (JSON object)"],"output_types":["JSON document structure with layer hierarchy","Component metadata and properties","Design tokens and style definitions","File metadata and version information"],"categories":["tool-use-integration","design-automation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-iflow-mcpfigma-mcp__cap_1","uri":"capability://tool.use.integration.mcp.tool.schema.generation.from.figma.api","name":"mcp tool schema generation from figma api","description":"Automatically generates MCP tool definitions that map Figma API endpoints to callable functions with proper parameter schemas, type hints, and descriptions. Uses MCP server specification to define tools with JSON Schema validation, allowing LLM clients to understand available operations and constraints before invocation.","intents":["Define what Figma operations an LLM agent can perform with proper type safety","Enable LLM clients to discover available Figma queries through tool introspection","Validate agent requests against Figma API constraints before execution","Generate human-readable tool descriptions for agent decision-making"],"best_for":["MCP client developers integrating Figma capabilities into LLM applications","Teams building agentic systems that need design file access","Design tool vendors implementing LLM-native integrations"],"limitations":["Tool schema generation is static — does not dynamically adapt to Figma API changes without server restart","Schema complexity limited by MCP specification constraints on parameter nesting depth","No automatic schema versioning — breaking API changes require manual schema updates"],"requires":["MCP server implementation (Node.js)","Figma API documentation or SDK reference","JSON Schema validation library","MCP client with tool calling support"],"input_types":["Figma API endpoint specifications (internal)","Parameter definitions and constraints (internal)"],"output_types":["MCP tool definition JSON with schema","Parameter validation rules","Tool descriptions and usage examples"],"categories":["tool-use-integration","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-iflow-mcpfigma-mcp__cap_2","uri":"capability://safety.moderation.figma.authentication.and.credential.management","name":"figma authentication and credential management","description":"Handles Figma API authentication through MCP server configuration, supporting personal access tokens and OAuth flows. Manages credential lifecycle (storage, refresh, expiration) and injects authentication headers into all Figma API requests transparently, isolating clients from credential handling complexity.","intents":["Securely store and manage Figma API credentials in MCP server configuration","Authenticate all Figma API requests without exposing tokens to LLM clients","Support multiple authentication methods (personal token, OAuth) for different deployment scenarios","Handle token refresh and expiration automatically"],"best_for":["Production deployments requiring secure credential isolation","Multi-tenant systems where each user has different Figma access","Teams deploying MCP servers in shared infrastructure"],"limitations":["Credentials must be configured at server startup — no runtime credential rotation without restart","No built-in credential encryption — requires external secret management (environment variables, secret stores)","OAuth flow requires user interaction for initial authorization, not suitable for fully automated systems","Single credential per server instance — multi-workspace scenarios require multiple server instances"],"requires":["Figma personal access token OR OAuth application credentials","Environment variable support or configuration file","MCP server runtime with credential injection capability","HTTPS for OAuth redirect URI (production)"],"input_types":["API token string (environment variable or config)","OAuth authorization code (for OAuth flow)","Figma workspace/team identifiers"],"output_types":["Authenticated HTTP headers","Token validity status","Authorization scope information"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-iflow-mcpfigma-mcp__cap_3","uri":"capability://tool.use.integration.figma.api.request.routing.and.error.handling","name":"figma api request routing and error handling","description":"Routes MCP tool invocations to appropriate Figma API endpoints, handles HTTP request/response cycles, and implements error recovery strategies. Translates Figma API errors into MCP-compatible error responses with context, enabling agents to understand failures and retry intelligently.","intents":["Execute Figma API calls triggered by LLM agent tool invocations","Handle network failures and API errors gracefully with retry logic","Translate Figma API error responses into actionable feedback for agents","Manage request rate limiting and backoff strategies"],"best_for":["Agentic systems that need resilient Figma integration","Production workflows where API failures must be handled gracefully","Teams building design automation with retry requirements"],"limitations":["Retry logic is server-side only — does not persist failed requests across server restarts","Rate limiting is per-server instance — distributed deployments need external rate limit coordination","Error context is limited to Figma API response — does not include agent-level context","Timeout handling is fixed — no per-request timeout customization"],"requires":["HTTP client library (Node.js built-in or axios/fetch)","Figma API endpoint URLs","Error handling middleware or try-catch patterns","Network connectivity to Figma API"],"input_types":["MCP tool invocation with parameters","Figma API endpoint and method","Request headers and authentication"],"output_types":["Figma API response data (JSON)","HTTP status codes and error messages","Retry status and backoff information"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-iflow-mcpfigma-mcp__cap_4","uri":"capability://search.retrieval.design.file.querying.with.layer.filtering.and.search","name":"design file querying with layer filtering and search","description":"Enables agents to query Figma documents with filtering capabilities, searching for specific layers, components, or design elements by name, type, or properties. Implements query translation to Figma API calls, supporting hierarchical traversal of document structure and component library lookups.","intents":["Find specific design components or layers by name or type in large Figma files","Query design system components and their properties for code generation","Retrieve all instances of a component to understand design consistency","Search for design elements matching specific criteria (color, size, text content)"],"best_for":["Design-to-code automation pipelines that need to locate specific components","Design system auditing tools that verify component usage","AI agents building design-aware applications"],"limitations":["Search is limited to Figma API capabilities — no full-text search across design content","Filtering is performed server-side after fetching full document — inefficient for large files (1000+ layers)","No fuzzy matching — searches require exact or prefix matches","Component instance resolution requires additional API calls per instance"],"requires":["Figma file ID with read access","Figma API token with file access permissions","Document structure already loaded or accessible via Figma API"],"input_types":["Query string (layer name, component name)","Filter criteria (type, properties)","Figma file ID"],"output_types":["Matching layer/component objects with metadata","Layer hierarchy and parent references","Component properties and design tokens"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-iflow-mcpfigma-mcp__cap_5","uri":"capability://data.processing.analysis.component.and.design.token.extraction","name":"component and design token extraction","description":"Extracts component definitions, design tokens (colors, typography, spacing), and style information from Figma files into structured formats. Parses Figma component metadata and applies design system conventions to normalize token names and values for downstream consumption by code generators or design tools.","intents":["Export design system components and tokens for code generation","Build design-to-code pipelines that consume Figma design tokens","Audit design system consistency by extracting all defined tokens","Generate design token documentation from Figma source"],"best_for":["Design systems teams automating token export workflows","Code generation tools that need design token input","Design-to-code platforms building on Figma as source of truth"],"limitations":["Token extraction depends on Figma naming conventions — no automatic normalization for inconsistent naming","Complex nested components may not extract cleanly — requires manual post-processing","Design token values are extracted as-is from Figma — no unit conversion or normalization","Component variants are extracted separately — no automatic variant grouping"],"requires":["Figma file with properly structured components and design tokens","Figma API access to component definitions","Knowledge of Figma naming conventions used in the file"],"input_types":["Figma file ID","Component or token name patterns","Design system structure definition (optional)"],"output_types":["JSON/YAML design token definitions","Component metadata with properties","Design system documentation","Code-ready token exports (CSS, TypeScript, etc.)"],"categories":["data-processing-analysis","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":24,"verified":false,"data_access_risk":"high","permissions":["Figma API token (personal access token or OAuth)","MCP client implementation (Claude Desktop, custom MCP host, or compatible LLM framework)","Node.js 16+ runtime environment","Network access to Figma API endpoints","MCP server implementation (Node.js)","Figma API documentation or SDK reference","JSON Schema validation library","MCP client with tool calling support","Figma personal access token OR OAuth application credentials","Environment variable support or configuration file"],"failure_modes":["Read-only introspection — no capability to modify or write changes back to Figma documents","Requires valid Figma API token with appropriate file access permissions","MCP protocol overhead adds latency compared to direct REST API calls","Limited to Figma API rate limits (120 requests per minute for standard tier)","Tool schema generation is static — does not dynamically adapt to Figma API changes without server restart","Schema complexity limited by MCP specification constraints on parameter nesting depth","No automatic schema versioning — breaking API changes require manual schema updates","Credentials must be configured at server startup — no runtime credential rotation without restart","No built-in credential encryption — requires external secret management (environment variables, secret stores)","OAuth flow requires user interaction for initial authorization, not suitable for fully automated systems","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.22,"ecosystem":0.3,"match_graph":0.25,"freshness":0.6,"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:23.903Z","last_scraped_at":"2026-05-03T14:23:42.969Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-iflow-mcpfigma-mcp","compare_url":"https://unfragile.ai/compare?artifact=npm-iflow-mcpfigma-mcp"}},"signature":"FIiecMMKD4mjiSw/uWAiGRIC3ouUIrQDkH6K8RIxlowjjpFxS1uzS+5qYsig53bwsYaV5YefuwYo+flowtTUBQ==","signedAt":"2026-06-22T04:35:45.304Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-iflow-mcpfigma-mcp","artifact":"https://unfragile.ai/npm-iflow-mcpfigma-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=npm-iflow-mcpfigma-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"}}