Layerwright logo

Layerwright

Converts HTML and Figma designs into editable Figma files and React code through a local MCP server and plugin.

Install Layerwright

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "layerwright": {
      "command": "npx",
      "args": [
        "-y",
        "layerwright"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 28 tools correctly (15d ago).

Overview

The layerwright MCP server connects Claude Code, Codex, or Cursor with a Figma plugin to move designs between HTML, Figma, and React code. It imports standalone HTML into editable Figma frames with Auto Layout, assets, text, vectors, and optional Design System components, while selected Figma frames can be inspected and implemented with existing React components and tokens. It runs locally through the Figma desktop plugin and localhost, without an API key, cloud account, or configurable port. Reach for it when an agent needs to create or adapt editable Figma work, synchronize it with a component library, or generate code from Figma designs.

Use cases

  • Import standalone HTML into editable Figma frames
  • Build screens from an existing Design System
  • Implement selected Figma frames with React components
  • Audit frames for variables, text styles, and component usage
  • Create mobile variants from selected Figma designs

Key features

  • HTML-to-Figma Auto Layout import
  • Figma-to-React component mapping
  • Design System synchronization
  • Pixel-faithful import mode
  • Prototype and interaction creation
  • Local multi-session Figma workflow

Tools28

What Layerwright lets your agent do. Expand a tool for its parameters.

Verified live~11.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

6/6 checks healthy over the last 21d

What it can do

From the 28 tools this server returned when we ran it.

Runs commands · 2Can delete or modify data · 2Handles credentials · 6Makes network requests · 2Read-only tools · 24
Network at startup4 connections
Files written at startup1
Install scriptsNone
npm provenanceSigned build
Package age23 days
Maintainers1

Observed 2026-10-22 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · layerwright (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars9Stargazers on the source repository.
npm downloads2.1kPackage downloads in the last 30 days.
Last commit25d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed28Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Layerwright works

What layerwright does

The layerwright MCP server provides a local bridge between AI coding sessions and Figma. Its paired Figma plugin can import standalone HTML as editable frames, including Auto Layout derived from Flexbox, text styling, images, SVG icons, CSS backgrounds, canvas content, gradients, borders, shadows, and responsive desktop and mobile layouts. Right-to-left text and visual order are supported for languages such as Persian, Arabic, and Hebrew.

The layerwright MCP server also supports prompt-driven design plans. Claude can produce a typed JSON design plan that is validated against the available Figma components, variables, and text styles before the plugin builds it. Plans can include prototypes, interactions, scrolling frames, flow starting points, and transitions. Existing designs can be edited, converted into components or variant sets, synchronized with a Design System, or exported back into an editable plan.

For the reverse workflow, Figma frames are inspected as structured plans. React or Next.js codebases can be scanned for exported components, including Tailwind and shadcn/ui usage. Confirmed mappings are stored in .layerwright/mapping.json, allowing generated implementations to reuse existing components and theme tokens rather than creating duplicate controls.

How it works

Run the MCP server from a project and open the Layerwright plugin in Figma desktop. Coding sessions join the local connection, and the plugin sends requests to the selected session. Multiple sessions and Figma files can be connected; each request is associated with the selected session and working file.

The plugin can send selected layers or custom requests such as building a mobile version, polishing a design, making a component, or implementing a frame in code. Text layers beginning with @<session> can also act as requests. Claude Code can be woken by the plugin monitor, while Codex receives requests on its next Figma step or through /layer:inbox.

Setup and configuration

Initialize Layerwright in the project with:

Terminal
npx layerwright init

Then open the plugin in Figma desktop. Plain HTML imports do not require an AI session and can be run with npx layerwright import ./design.html --to-figma. To install fonts shipped with an export, use npx layerwright fonts ./export --install.

The layerwright MCP server uses the local machine and the plugin communicates only with localhost. The documented workflow requires no API key, cloud account, or manually configured port. A Design System scan and component mappings are needed when imports or generated code should use an existing component library.

Tools and capabilities

Named MCP operations include:

  • import_html_to_plan for converting HTML into a structured design plan.
  • figma_import_html for pixel-faithful imports and review boards.
  • figma_import_assets for placing SVGs and images into a Figma page.
  • figma_analyze_design for Design System synchronization and audits.
  • figma_edit for modifying existing Figma frames in one undo step.
  • figma_inspect for reading a frame as a design plan.
  • code_scan_components for finding components in a codebase.
  • code_mapping for saving confirmed Figma-to-code mappings.
  • code_verify_usage for checking component reuse and flagging raw or arbitrary implementations.

The layerwright MCP server also supports prototypes, asset conversion, Figma-to-plan export, component instances, variables, text styles, and AI cursor feedback in the plugin window and canvas.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Layerwright

layerwright is an MCP server that connects Claude Code, Codex, and Cursor with a Figma plugin. Its main tools import HTML and assets into editable Figma frames, inspect and edit Figma designs, synchronize Design System components, map Figma components to React code, and verify component usage locally without API keys or a cloud account.

Run `npx layerwright init` in your project, then open the Layerwright plugin in Figma desktop. For a direct HTML import, use `npx layerwright import ./design.html --to-figma`; no AI session is required for that plain import.

Yes, layerwright works with Cursor, as well as Claude Code and Codex. Sessions on the computer share the local connection to the Figma plugin, and requests from the plugin window can be sent to the selected session.

Yes, layerwright can implement a selected Figma frame with mapped React components and theme tokens. `figma_inspect`, `code_scan_components`, and `code_mapping` support the workflow, while `code_verify_usage` checks whether existing components were reused.

No, layerwright does not require an API key, cloud account, or manually configured port. The workflow runs on the local machine, and the Figma plugin communicates with localhost.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLayerwright AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/layerwright?style=directory)](https://allmcps.com/mcp/layerwright)
HTML Embed
<a href="https://allmcps.com/mcp/layerwright"><img src="https://allmcps.com/api/badge/layerwright?style=directory" alt="Layerwright on AllMCPs" /></a>