Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"FigmaEdit": {
"args": [
"-y",
"figma-edit-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Connect AI assistants to Figma via Model Context Protocol to read designs, create and modify elements, and manage design systems programmatically.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'figma-edit-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 figma-edit-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
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
Swirl Design System AI package with artifacts for AI agents
GoPeak — The most comprehensive MCP server for Godot Engine. 95+ tools, LSP, DAP, screenshots.
shadcn/ui for Laravel Blade — discover, read and install BlatUI components, blocks and charts.
MCP Security Weekly
Get CVE alerts and security updates for io.github.neozhehan/figma-edit-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Connect AI assistants to Figma via Model Context Protocol to read designs, create and modify elements, and manage design systems programmatically.
This plugin empowers your AI assistant to become a Figma assistant, executing design updates Safer, Cleaner, and Faster than a human ever could.
This plugin allows you as a Designer to focus purely on creative decision-making, leaving the error-prone & repetitive manual changes to the automated systems.
📖 Documentation: neozhehan.github.io/figma-edit-mcp
Read more about our design philosophy here.
Every other way to give an AI write access to your Figma file trusts the AI to behave. This one doesn't — and that's the whole point.
An AI agent is one hallucination away from deleting the wrong layer, overwriting a shared component, or quietly mangling a design-system token — and you may not notice until the damage is downstream. Figma Edit MCP treats the agent as untrusted with respect to edit safety, and puts a gate it cannot bypass in front of every write. The agent never decides what's safe; the plugin does, and it refuses anything outside the lines — with a structured error, not a guess.
What the agent physically cannot do to your file:
And it's honest about its limits: it guarantees where, which node, and what kind of edit happens — not whether a valid, in-bounds edit was the one you actually meant. You stay in charge of intent; it removes the accidents.
📖 The full contract — every guarantee, the conditions it holds under, and exactly how each is enforced — lives in SAFETY.md. (Your agent loads the same rules at runtime via the figma-edit skill or figma-edit://guide/*.)