Reqwise Figma MCP
This server connects AI agents to a Figma canvas through MCP, letting them safely read, draw, and verify Figma designs.
Connection diagnostics:
figma_statusreports plugin health, leader/follower mode, queue, and next-step hints.Read the canvas:
figma_readsupports document info, selection, node lookup, search, text scanning, styles, variables, components, design-system snapshots, screenshots, exports, fonts, and layout audits.Draw and edit:
figma_writeruns modern JavaScript against afigma.*proxy to create/modify frames, text, shapes, apply variables, batch operations, and inspect layouts, with persistent per-sessionstate.Design rules:
figma_rulesreturns a markdown rule sheet of styles, variables, and components so agents reuse existing design tokens.On-demand docs:
figma_docsprovides guidance for rules, layout, API, tokens, icons, and recipes.
Allows AI agents to read and draw on the Figma canvas safely, with features like layout auditing, overlay creation, persistent session state, and batch operations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Reqwise Figma MCP run a layout audit on the selected frame"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Reqwise Figma MCP

An MCP server that lets AI agents read and draw on the Figma canvas — safely. Open source (MIT).
Need BPMN, UI templates, a 1-to-1 code ↔ Figma component map, design systems, journey maps, personas, accessibility and responsive audits, or self-playing demos? They are in Reqwise Figma MCP Pro →. Compare the two editions below.
Reqwise Figma MCP pairs a local MCP server with a companion Figma plugin. Point Claude Code, Cursor, Codex or any MCP-capable agent at it, and the agent can inspect a Figma file and draw into it by executing JavaScript against a figma.* proxy API — with the plugin layer catching the mistakes that usually turn "AI draws a screen" into "AI draws an overflowing, half-clipped mess." It also draws the BA diagrams a spec needs — userflow, activity, sequence, ERD, sitemap, state machine — and proof-reads the model behind each one.
It exists because the current generation of Figma MCPs make agents responsible for discipline they don't have: remembering never to overlay a semi-transparent frame, re-declaring token maps every call, manually computing x/y offsets, eyeballing screenshots to check for clipping. Reqwise moves that discipline into the server and plugin, and gives the agent a structured way to verify its own work.
Free vs Pro

Feature | Free | Pro |
Connection | ||
Figma bridge with rich diagnostics and next-step hints | ✅ | ✅ |
Several Figma windows and several AI agents at once (leader/follower) | ✅ | ✅ |
One launcher for Claude Code, Cursor and Codex | ✅ | ✅ |
Hardened local bridge (sandboxed JS, authenticated forwarding) | ✅ | ✅ |
Rule sheet and on-demand docs for the agent | ✅ | ✅ |
Read and draw on the canvas | ||
Read pages, layers, selection; screenshots and exports | ✅ | ✅ |
Draw and edit frames, text, shapes; streaming batches | ✅ | ✅ |
Layout audit — overflow, clipping, truncated text | ✅ | ✅ |
New work never lands on top of existing work | ✅ | ✅ |
Tokens and variables — create, bind, edit, import/export | ✅ | ✅ |
Text styles and effect styles | ✅ | ✅ |
Icons, images, overlays, gradients, recolor | ✅ | ✅ |
Prototype reactions | ✅ | ✅ |
Delete pages and styles, sweep unused styles | ✅ | ✅ |
Read an existing design system; export design-kit.md | ✅ | ✅ |
Components — find, create, variants, instances | — | ✅ |
Component properties — booleans, nested instances, edit/delete | — | ✅ |
Design-system compliance audit and auto-binding | — | ✅ |
BA diagrams | ||
Userflow | ✅ | ✅ |
Activity diagram with swimlanes | ✅ | ✅ |
Sequence diagram | ✅ | ✅ |
ERD | ✅ | ✅ |
Sitemap | ✅ | ✅ |
State machine | ✅ | ✅ |
Arrows follow the boxes; edit a diagram in place | ✅ | ✅ |
Cross-check diagrams against each other | ✅ | ✅ |
Use case diagram | — | ✅ |
BPMN process diagram — pools, lanes, events, gateways, message flows | — | ✅ |
User journey map (several layouts and themes) | — | ✅ |
Persona set | — | ✅ |
Design system | ||
Generate a design system — 60 components, tokens, screen grids, doc pages | — | ✅ |
10 visual styles, side-by-side preview, AI style recommendation | — | ✅ |
Learn a system from the canvas or from design.md | — | ✅ |
1-to-1 map between your code components and Figma components — props ↔ variants, kept in sync both ways | — | ✅ |
The tool asks the user the right questions, with time estimates | — | ✅ |
UI templates | ||
Section and block templates — hero, nav, pricing, data table, form, empty state | — | ✅ |
Templates drawn with your components and tokens, not pasted stock art | — | ✅ |
Start a design system from a template — palette and visual style preconfigured | — | ✅ |
Quality and presentation | ||
Accessibility audit — contrast, touch targets, unnamed controls | — | ✅ |
Responsive audit — stretch a screen, compare mobile and desktop | — | ✅ |
Self-playing prototype demos | — | ✅ |
Record a demo to video | — | ✅ |
Claude skills | ||
/figma-userflow, /figma-activity, /figma-sequence, /figma-erd, /figma-sitemap, /figma-state | ✅ | ✅ |
/figma-usecase, /figma-journey, /figma-persona, /figma-design-system, /figma-demo | — | ✅ |
Get Pro → — this table is generated from the feature list both editions ship from, so it is current with every release.
Related MCP server: F-MCP (Figma MCP Bridge)
Why this one
Typical Figma MCP | Reqwise Figma MCP | |
Verification | Screenshot only — agent eyeballs pixels |
|
Overlays / scrims | Agent dims a screen with an opacity'd FRAME (dims the whole subtree) |
|
Session state | Token maps and id registries re-declared every call |
|
Connection | Silent boolean, or a dead WS with no explanation |
|
Multiple IDE windows | Second server instance fights for the port or silently fails | Leader/follower election; followers forward through an authenticated |
Batch operations | Hard caps (e.g. 50 ops) with all-or-nothing failure | Chunked streaming, partial commit, exact per-index error reporting, no hard cap |
Structural frames | Figma's default white fill turns layout wrappers into accidental white slabs | FRAME/COMPONENT without an explicit fill defaults to transparent; visible surfaces opt in |
Sandbox JS | Restricted/older syntax (no | Node |
Errors | Bare exceptions | Every failure carries |
Edit-in-place | Draw-from-scratch focus; per-op fights the single-threaded plugin | Selection-first workflow ( |
Diagrams | Mermaid/plantuml text rendered to an image — each diagram an island | Every diagram frame stores the model it was drawn from: change one with |
Business rules with a number | The |
|
See ARCHITECTURE.md for the full design rationale and the root-cause fixes behind these defaults.
Quickstart

git clone https://github.com/hoangpm96/reqwise-figma-mcp.git
cd reqwise-figma-mcp
npm install
npm run buildThis builds the server to dist/ and the plugin bundle to plugin/code.js.
Register the MCP server — all editors at once (Cursor, Claude Code, Codex):
npm run install:mcpor one editor by hand:
claude mcp add reqwise-figma -s user -- /absolute/path/to/reqwise-figma-mcp/scripts/reqwise-mcp.shImport the plugin into Figma Desktop: menu → Plugins → Development → Import plugin from manifest… → select plugin/manifest.json. Run it from Plugins → Development → Reqwise Figma MCP and keep its window open.
Check the connection: ask your agent to call figma_status. Full walkthrough and troubleshooting: docs/SETUP.md and docs/INSTALL.md. Several editors at once: docs/MULTI-AGENT.md.
Every session: open your Figma file → Plugins → Development → Reqwise Figma MCP → leave the window open. Figma doesn't auto-start plugins.
Tools
Tool | Purpose |
| Rich connection diagnostics — plugin connection, leader/follower mode, heartbeat, queue, sessions, and an ordered |
| Read the canvas via an |
| Execute modern-ES JavaScript against the |
| One-call design-system rule sheet (styles + variables + components) as markdown — read before drawing so you reuse instead of hardcode. For a durable spec, use |
| Draw six diagram kinds from a model you derived from the spec, each with findings on the content, not the drawing. |
| On-demand documentation: |
Full parameter reference for every operation and every figma.* method: docs/TOOLS.md. Pro adds figma_design_system and figma_record, four more diagram kinds (use case, BPMN, journey map, persona set), the UI templates, the code ↔ Figma component map and the audits — see Free vs Pro.
Diagram skills
.claude/skills/ ships a skill per diagram kind — /figma-userflow, /figma-activity, /figma-sequence, /figma-state, /figma-erd, /figma-sitemap — plus the discipline they share (the connection gate, the four levels of "correct", the findings loop, verification). Copy them into .claude/skills/ in your project. See .claude/skills/README.md.
Example: figma_write
// Set tokens once — they persist in this session's `state.tokens`.
await figma.setupTokens({
colors: { primary: "#2563EB", surface: "#0B0B0F" },
numbers: { "radius-md": 8 },
});
// Draw a card with wrapping text, reusing the parent's width.
const card = await figma.create({
type: "FRAME", name: "Card", parentId: state.rootId,
width: 320, layoutMode: "VERTICAL",
});
await figma.applyVariable(card.id, "fills", "surface");
await figma.create({
type: "TEXT", parentId: card.id, wrap: true,
characters: "A long paragraph that must wrap inside the card.",
});
// Verify before screenshotting for a human.
const audit = await figma.layoutAudit(card.id);
if (audit.summary.issues.length) console.warn(audit.summary.issues);Example: snapshot a design system to design-kit.md
Ask your agent to call:
{ "op": "generate_design_md", "params": { "depth": 3, "includeAnatomy": true, "includeScreens": true } }The response contains a source-grounded markdown snapshot: extraction coverage, colors,
typography, observed layout frequencies, screen composition evidence, local and
remote component usage, exact node ids/keys/variant ids/property keys, ready-to-run
instantiate examples, reuse rules, responsive evidence and known gaps. Save
it in the target codebase as design-kit.md before asking the agent to create UI
from an existing Figma component system. Facts are separated from observations and
unknown UX semantics. For a very large file, tune maxComponents, maxScreens,
maxInstances or maxOutputChars; output limits omit complete sections rather
than cutting Markdown mid-table/code-block.
design.mdanddesign-kit.mdare two different files — human intent vs. machine snapshot, likepackage.jsonvs.package-lock.json. The tools never overwritedesign.md. See the two-file workflow.
Architecture
MCP client (Claude Code / Cursor)
│ stdio (MCP)
▼
Reqwise MCP server (Node ≥ 18, TypeScript)
│ owns HTTP+WS server on localhost:38470 (fallback +1..+9)
│ GET /health → diagnostics JSON
│ POST /rpc → follower → leader forwarding (auth token)
│ WS /ws → Figma plugin UI connection
▼
Figma Desktop plugin
├── ui.html (WebSocket client, heartbeat, reconnect w/ backoff)
└── code.js (Plugin API executor, safe-default handlers)Every operation — leader-direct or follower-forwarded — passes through one validateOperation() choke point before it reaches the plugin. Full topology, the leader/follower protocol, and the 15 safe-default fixes are documented in ARCHITECTURE.md.
Documentation
docs/SETUP.md— start here: install, daily routine, troubleshootingdocs/INSTALL.md— installation reference: env vars, port behaviour, leader/followerdocs/TOOLS.md— full tool +figma.*API reference, error codesdocs/MIGRATION.md— migrating fromfigma-ui-mcpdocs/RECIPES.md— practical cookbookdocs/DEMO-PROMPT.md— a paste-ready prompt that demos every free diagram kind plus mobile screensARCHITECTURE.md— design goals and internals
Reqwise Figma MCP Pro
Pro is the full edition, built by the same author on this same core: a design-system generator with ten visual styles, use case and BPMN diagrams, journey maps and persona sets, component authoring, UI section and block templates that draw with your own components and tokens (and design-system templates that come with palette and visual style preconfigured), a 1-to-1 map between your code components and their Figma counterparts (props ↔ variants, so generated UI matches the codebase instead of resembling it), accessibility and responsive audits, self-playing demos and demo videos. ai4ba.com/figma-mcp
License
MIT — see LICENSE. Reqwise Figma MCP Pro is a separate, commercially licensed product.
Available Tools
5 toolsfigma_docsA
On-demand documentation for this API and its safe-by-default rules. Sections: rules | layout | api | tokens | icons | recipes.
Inputs: section (required).
figma_readA
Read the Figma canvas with a token-frugal response. Choose an operation and pass its params. layout_audit is the structured verify tool (declared vs rendered bounds, overflow, clipping, truncation). read_selection deep-reads the current selection in one call — the entry point of the selection-first edit-in-place lifecycle (read_selection → figma_write modify → layout_audit).
Inputs: op (required), params.
figma_rulesA
One-call design-system rule sheet as markdown: styles + variables + components, fetched in parallel. Read before drawing so you reuse tokens/components instead of hardcoding.
Inputs: no named parameters.
figma_statusA
Rich connection diagnostics for the Figma bridge (never a bare boolean): plugin connection, leader/follower mode, port, heartbeat, queue, sessions, and an ordered list of concrete next-step hints when something is off.
Inputs: no named parameters.
figma_writeA
Execute modern-ES JavaScript in a sandbox against the figma.* proxy to draw/modify the canvas. state persists across calls in a session. Banned: require/process/fetch/timers/eval. Returns { ok, result, logs, warnings }.
Inputs: code (required), sessionId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: docs for API reference, read for canvas reading, rules for design systems, status for diagnostics, and write for modifications. No overlap.
All tools follow a consistent figma_verb naming pattern (figma_docs, figma_read, figma_rules, figma_status, figma_write), making it easy to infer functionality.
5 tools is well-scoped for a Figma MCP server, covering essential operations without unnecessary bloat.
The set covers reading, writing, documentation, rules, and status. While minor operations like explicit deletion or search are missing, the core lifecycle is covered.
Maintenance
Related MCP Connectors
Design canvas for agents: create, edit, render and export Figma-shaped designs over MCP.
Give your agent a real design system: tokens, measured WCAG contrast, and rules to follow.
Your AI agent designs editable, clickable UI prototypes on a live canvas.
Give AI agents your deeepSpace design system: components, tokens, styles and code mappings.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Figma to create, read, and manage designs using the Figma REST API and a dedicated plugin. It supports advanced features like UI generation from text, webpage reconstruction in Figma, and design token synchronization with codebases.20MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to read, analyze, and modify Figma designs, manage design tokens, and create prototype connections, all while keeping data local.6344 npm10MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect Figma selections, navigate pages, render previews, generate starter code, and submit user-approved canvas edits through a local bridge.3 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, analyze, and modify Figma designs, including bulk style updates, accessibility audits, comment triage, and code generation from designs.842 npmMIT