MCP server

Figma Bridge MCP: Build and Import Figma Pages Locally

The figma-bridge MCP server connects an AI coding agent to Figma Desktop's Plugin API, so it can build layouts, import a website and audit a design with no rate limit.

Run
npx @clovis500c/figma-bridge setup
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the figma-bridge MCP server?

figma-bridge is a local MCP server set up with npx @clovis500c/figma-bridge setup, paired with a Figma plugin that stays open in Figma Desktop. Because it works through the Plugin API rather than the web API, it has no rate limit, and gives an agent 29 tools to build layouts, import a website as editable frames, audit a design and export code.

figma-bridge connects an agent to Figma Desktop through the Plugin API rather than the Figma web API, so it keeps working inside a design session without hitting an external rate limit.

Beyond reading and writing a canvas, it can pull in an existing website as editable frames, run a design audit against a project's own tokens, and export the result as code for several frameworks.

What it changes in your workflow

  • An agent builds a full layout from a JSON specification instead of placing elements one call at a time.
  • A live website can be imported as editable frames, turning an existing page into a starting point.
  • A design audit checks a page's health against the project's own design system before it ships.
  • The same design can export as code for a framework, or as Roblox UI for a different target.

What it does, by group

GroupTools
Buildbuild, prototype, insert_icon, annotate
Importimport_web, get_design_system, design_tokens
Checkaudit, describe, find, compare, screenshot
Exportexport_code, export_roblox, run_script, checkpoint

Who it is for

Best for

  • Teams that hit Figma's web API rate limit often and want a local path around it.
  • Turning an existing live website into editable Figma frames as a starting point.
  • Running a design-system audit on a page before calling a design finished.

Not for

  • Treating a Figma design and a live website as one connected design graph, rather than a one-time import, is the broader model Plumb MCP builds around.
  • Editing and auditing a design through tool names and a shape different from this bridge's 29 is the approach the Relai MCP server takes for the same Figma Desktop target.
  • Operating Figma Desktop through a different agent-driven setup than this bridge's plugin pairing is how Conduit Design MCP lets an agent work the canvas.
  • Converting Figma designs to code and back through a different local bridge mechanism, rather than this project's build and import tools, is what Figbridge MCP does.

Use it with UiChemy

This bridge builds and audits a design inside Figma itself. Once a layout is ready, UiChemy Figma to WordPress turns it into an editable Elementor or Gutenberg page. Click Get Started on uichemy.com.