MCP server that reads local Figma .fig files, fully offline
MCPpedia last refreshed this data
io.github.ntson9p/figme-mcp is an MCP server that MCP server that reads local Figma .fig files, fully offline. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 85/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"figme": {
"args": [
"-y",
"figme-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server that reads local Figma .fig files, fully offline
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked figme-mcp against OSV.dev.
Click any tool to inspect its schema.
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.
Image & PDF tools for AI agents: compress, convert, resize, PDF, AI vision, pipeline.
MCP Security Weekly
Get CVE alerts and security updates for io.github.ntson9p/figme-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server that lets your AI agent read Figma .fig
files — offline, with no Figma account or API token.
Save a design from Figma as a .fig file, and your agent can read everything in it: layers and
layout, colours, text, components, design tokens and images. figme can also draw any frame as a
picture, so the agent can compare what it built with the design.
you: "what does the tab component in design.fig look like?"
fig_overview → 10 pages, 2,046 components, 273 variables, 212 images
fig_find → "lv2/tab/large" is 2:1337, on page "Page 1"
fig_style → display:flex, direction:row, gap:8, padding:"8px 16px",
cornerRadius:4, stroke #FFFFFF bound to variable "tab/large/underline"
(active #FFFFFF / inactive #333333)
fig_render draws any layer as a PNG or SVG..fig carries the schema that describes it, and figme decodes
the file with that schema, so fields Figma adds later don't break it.You need Node.js 22.15 or newer.
1. Save the design as a .fig file. In Figma, choose File → Save local copy… If it's a
Community file, click Open in Figma first.
2. Add figme to your agent. In Claude Code:
claude mcp add figme -- npx -y figme-mcp
For Cursor, VS Code, Windsurf and other clients, see Set up your client.
3. Ask. Give the full path to the file, and paste a Figma link if you have one:
Using figme, read /Users/me/Desktop/App.fig and build this frame as a React component: https://www.figma.com/design/AbC123/App?node-id=3017-121
The agent picks the tools from there. A few more things to try:
Every client runs the same command, npx -y figme-mcp. Only the place you put it changes.
claude mcp add figme -- npx -y figme-mcp # this project
claude mcp add -s user figme -- npx -y figme-mcp # every project
To share the server with everyone who works on a repository, commit a .mcp.json at its root:
{
"mcpServers": {
"figme": { "command": "npx", "args": ["-y", "figme-mcp"] }
}
}
The Claude Code extensions for VS Code and JetBrains use this same configuration. They don't read the editor's own MCP settings.
Add this to ~/.cursor/mcp.json for every project, or to .cursor/mcp.json for one:
{
"mcpServers": {
"figme": { "command": "npx", "args": ["-y", "figme-mcp"] }
}
}
<detail