kaiuwehella/figma-bridge-mcp
Local, authenticated Figma bridge with exact design-to-code and code-to-Figma workflows.
Use when creating or updating a Figma screen, page, modal, panel, or other composed view from an existing codebase or running UI with the Figma Bridge MCP, including requests such as "code to Figma", "push this screen to Figma", "make Figma match the app", or "create this page in Figma". Preserve semantic Auto Layout/Grid, source assets, project tokens, existing Figma components, and Design Entity identity. Do not use when the primary deliverable is a new reusable component library; use figma-bridge-component-library instead.
Use when creating or updating reusable Figma components, component sets, variants, component properties, variables, styles, themes, or a design-system library from code with the Figma Bridge MCP. Trigger for requests such as "create this component in Figma", "build variants", "turn our code components into a Figma library", "add component properties", or "sync our design system to Figma". Enforce foundations-first token bindings, identity-safe reuse, sequential writes, and per-component visual validation. Do not use merely to compose a screen from components that already exist.
Use when implementing a Figma frame, screen, or component as code with the Figma Bridge MCP, including requests such as "implement this Figma design", "build this screen", "design to code", or a figma.com node URL alongside a codebase. Enforce source-asset fidelity, the target project's existing stack, scoped and token-efficient reads, optional section-level parallel agents, and build plus pixel-diff verification. Do not use for the reverse code-to-Figma direction.