Bidirectional Figma MCP — AI draws UI on Figma canvas, reads designs back
MCPpedia last refreshed this data
io.github.nguyendinhphongdx/figma-bridge-mcp is an MCP server that bidirectional Figma MCP — AI draws UI on Figma canvas, reads designs back. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 58/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"figma": {
"args": [
"-y",
"@hanoilab/figma-bridge-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Bidirectional Figma MCP — AI draws UI on Figma canvas, reads designs back
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y '@hanoilab/figma-bridge-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @hanoilab/figma-bridge-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in design
Design tokens from any live site: colours, type, spacing, components, drift against a baseline.
Draw and visually collaborate with your agents on tldraw's canvas.
MeiGen-AI-Design-MCP — Turn Claude Code / OpenClaw into your local Lovart. Local ComfyUI, 1,400+ prompt library, multi-direction parallel generation.
Inspect and edit Three.js scenes, materials, shaders, lights in real time from any AI agent
MCP Security Weekly
Get CVE alerts and security updates for io.github.nguyendinhphongdx/figma-bridge-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A bidirectional Model Context Protocol bridge for Figma Desktop.
No Figma API key. No cloud. Everything runs on localhost.
Quick start · How it works · Tools · Security · Troubleshooting · Changelog
Not affiliated with, endorsed by, or sponsored by Figma, Inc. "Figma" is a trademark of Figma, Inc., used here only to describe compatibility.
figma-bridge-mcp connects an AI assistant to the document you have open in Figma Desktop.
| ✍️ Write | The AI runs JavaScript against a figma.* API to create frames, text, vectors, components, variables, prototypes. |
| 👀 Read | The AI extracts node trees, resolved design tokens, CSS, component maps and screenshots — ready for design-to-code. |
| 🔒 Local | The bridge listens on 127.0.0.1 only. Nothing leaves your machine. |
| 🧩 Any MCP client | ✅ Tested with Claude Code and Antigravity. 🔧 Compatible with Cursor, VS Code, Windsurf, Zed and any stdio MCP client. |
Requires Figma Desktop. The plugin talks to the server over
localhost, which Figma's web app does not allow.
Three parts cooperate: your AI client, the MCP server (Node), and the Figma plugin (inside Figma Desktop). The plugin polls the server, so no inbound connection to Figma is ever needed.
flowchart LR
subgraph Client["AI client"]
A["Claude Code · Cursor · Windsurf<br/>VS Code · Antigravity · any MCP client"]
end
subgraph Server["figma-bridge-mcp (Node)"]
B["MCP server<br/>5 tools · stdio"]
C["Code sandbox<br/>runs figma_write code"]
D["HTTP bridge<br/>127.0.0.1:47451"]
end
subgraph Figma["Figma Desktop"]
E["Plugin UI<br/>long-poll client"]
F["Plugin main thread<br/>66 operations"]
G[("Figma document")]
end
A <-->|"MCP / stdio"| B
B --> C
C --> D
B --> D
D <-->|"HTTP long-poll"| E
E <-->|postMessage| F
F <--> G
The server holds each poll open for up to 8 s and answers the moment work is queued, so latency is typically under 100 ms.
sequenceDiagram
autonumber
participant AI as AI client
participant S as MCP server
participant B as Bridge :47451
participant P as Figma plugin
AI->>S: figma_write { code }
S->>S: run code in sandbox
S->>B: queue operation (create, modify, …)
P->>B: GET /poll (held up to 8 s)
B-->>P: operations
P->>P: apply to the Figma document
P->>B: POST /response { id, data }
B-->>S: resolve operation
S-->>AI: result + logs
Each open plugin instance registers its own session. Pass the optional sessionId to figma_write / figma_read to target a specific file; if that session is not connected the call fails instead of writing into another file.
claude mcp add figma-bridge-mcp -- npx @hanoilab/figma-bridge-mcp # this project
claude mcp add --scope user figma-brid
... [View full README on GitHub](https://github.com/nguyendinhphongdx/figma-bridge-mcp#readme)