Layerwright vs Mimic AI
A side-by-side look at the Layerwright and Mimic AI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LayerwrightArchitecture & DesignTurn Claude Design and Claude Code designs into native, editable Figma files (HTML to Figma with Auto Layout and your Design System components), and Figma frames into code that uses your own React components. An MCP server and Figma plugin for Claude Code53GoodAuth: no auth requiredVerdict: choose Layerwright for architecture & design work; choose Mimic AI for architecture & design as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
LChoose Layerwright when
- You need dedicated capabilities in the Architecture & Design domain.
- Its auth model fits you: No auth required.
- You want tools like
import_html_to_plan, figma_execute_plan, figma_preview_plan.
Choose Mimic AI when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- You want tools like
mimic_status, mimic_discover_ds, figma_preload_styles.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Layerwright | |
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 53/100 · Good | 60/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9 | 14 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 16 | 60 |
| Full listing | View Layerwright | View Mimic AI |
Tools & capabilities
Layerwright tools 16
import_html_to_planHTML file or folder → editable Design Plan (Auto Layout, DS components, your own mappings). Returns a `planIdfigma_execute_planBuilds a plan in Figma: one undo step, rollback on failure, automatic verificationfigma_preview_planValidates and resolves a hand-written plan and returns a summaryfigma_editRename, move, duplicate, set, delete, resize to fit, group / ungroup, boolean shapes, componentize (variants, text properties), swap instances, bind variables, apply styles, annotations, prototype links and flowsfigma_export_imageA node as an image; compared with the source HTML or another node, with a diff heatmap. `save: true` writes it to `.layerwright/exports/` to show the userfigma_inboxRequests the user sent from the Figma window to this session, and the answer shown back in the windowfigma_statusConnection, page and the open Figma files (`file` to switch), Design System scan (components, variants, variables, styles, duplicate names), task-scoped contextfigma_inspectSnapshots (tree, summary, text, instances, or the subtree as a plan, saved to a file with `save`), plan-vs-canvas checks, select and zoom (switches page)figma_linkLinks to the selection, layers or the page, and the file's own link. Any layer argument also takes a Figma linkfigma_analyze_designAudit a frame against the DS, or `mode: "sync"` after an import; apply the groups you approvefigma_import_htmlPixel-faithful import, page setup, variables and text stylesfigma_import_assetsIcons and pictures from files or folders: SVGs as vectors (or components), PNG/JPEG/GIF/WebP/AVIF as images, in a grid- +4 more on the listing page
Mimic AI tools 60
mimic_statusReturns plugin connection status, current build phase, enforcement profile, knowledge store summary, and a contextual hint for what to do next.mimic_discover_dsComplete DS discovery in two steps. Step 1: call with fileKey — discovers variables, text styles, components via plugin API, caches everything, stays at Phase 1. Step 2: call again with communitySearchResults (library names from Figma MCP search_design_system) — verifies no community libraries were missed, then advances to Phase 2 (build-ready). Build tools are BLOCKED until Step 2 completes. If a community library's variables are not discoverable via the plugin API (communityVariablesRequired response), fetch them via Figma MCP search_design_system and pass as externalVariables.figma_preload_stylesSends text style keys to the plugin for caching. Call during DS setup phase.figma_preload_variablesStores DS variables in the local cache for enforcement and resolution.figma_set_session_defaultsComputes the enforcement profile from cached DS data and sends it to the plugin. Advances to Phase 2 (inventory ready).figma_list_text_stylesReturns all cached text styles from the DS.figma_preload_fill_stylesPreloads fill (color) styles into the DS cache from a library file key. Call when discovery missed fill styles (e.g. library variables not enumerable but fill styles exist in the REST API).figma_list_fill_stylesReturns all cached fill (color) styles from the DS. Use the style key as fillStyleId in create_frame, create_text, create_rectangle, create_ellipse, or set_node_fill.figma_discover_library_stylesDiscovers and caches text styles from a Figma library file.figma_discover_library_variablesDiscovers and caches variables from a Figma library file.figma_discover_library_componentsScans existing component instances on the current page to discover available DS library components, their keys, and variant properties. Call during DS discovery phase.mimic_map_componentsMaps HTML element types to DS component keys. Call once to get initial mapping. If FIGMA_TOKEN is configured (REST API discovery), all library components are already cached — missing types after the first call are confirmed gaps, proceed to build. If REST API is not available (no token), search the library via Figma MCP search_design_system for missing types, then call AGAIN with librarySearchResults to confirm gaps.- +48 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Layerwright
No confirmed install command for Layerwright yet — follow the setup steps linked from its listing page rather than a guessed package name.
Mimic AI
{
"mcpServers": {
"mimic-ai": {
"command": "npx",
"args": [
"-y",
"@miapre/mimic-ai"
]
}
}
}
Frequently asked questions
Layerwright is categorized under Architecture & Design and uses an install path we have not confirmed yet. Mimic AI belongs to Architecture & Design and uses a local stdio subprocess. Pick Layerwright for architecture & design work and Mimic AI for architecture & design.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Layerwright has no confirmed install command yet — follow its own setup instructions.
Layerwright is listed as free. Auth: no auth required. Mimic AI has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add layerwright and mimic-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Layerwright has a quality signal of 53/100 (Good) with 0 views, 0 installs and 9 GitHub stars. Mimic AI has 60/100 (Good) with 1 views, 0 installs and 14 GitHub stars.