Figme MCP server

figme — read local Figma .fig files from an AI agent

figme is an MCP server that lets an AI agent read everything inside a local .fig / .figma file — document structure, geometry, fills, strokes, effects, auto-layout, text (including mixed-format runs), components and instances, variables, prototype links and embedded bitmaps.

It is fully offline. No Figma account, no access token, no REST API, no network at runtime. It parses the file's own bytes, using the Kiwi schema that Figma ships inside every .fig.

It is also token-aware: the reference file used to develop it holds 116,142 nodes, and no tool response ever exceeds ~20 KB. Everything is shallow by default, filterable, and paginated with cursors.

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)

Non-goals

These are deliberate, permanent limits — not missing features:

frames, but it does contain everything needed to draw them again: Figma bakes outlined strokes, combined booleans, per-glyph outlines and per-instance geometry into the file at save time. fig_render uses that to produce a real picture offline — see Rendering for exactly what is exact and what is approximated. It is not a screenshot of Figma and never will be: read the report before trusting fine detail.

• Rendering is best-effort, not pixel-perfect. A .fig contains no rendered pixels of your

server are figimage { savePath } and figrender { savePath }, which write to a path you name.

• No writing. Nothing is ever written back into a .fig. The only write paths in the whole

from other files (styles, variables, components) cannot be resolved offline; they come back as their opaque assetRef so you can see that they exist and where they point.

• No Figma API and no network. Nothing here talks to figma.com. Library assets published

fignode reports the blob indices and figblob hands you the raw bytes, but this server does not interpret them.

• No vector-network decoding (v1). Vector geometry lives in a separate binary blob format.

• Not a diffing or version-history tool. A saved .fig is a full snapshot, not a delta.

Requirements

Node built-ins.

• Node.js ≥ 22.15 (needs zlib.zstdDecompressSync; developed on Node 24).
• Runtime dependencies: @modelcontextprotocol/sdk and zod. The parser itself uses only

Install

figme is published on npm, so there is nothing to clone and nothing to build — your MCP client downloads it on first start with npx.

You need two things:

there is no account, token or sign-in — but there is also nothing to read until you save one. In Figma: File -> Save local copy....

• Node.js >= 22.15 (see Requirements above).
• A .fig file on disk. This server reads a local file and never contacts figma.com, so

The part every client shares

Nearly every MCP client spawns a stdio server from the same two fields:

{ "command": "npx", "args": ["-y", "figme-mcp"] }

On Windows, some clients cannot resolve npx on their own. If the server fails to start, route it through cmd:

{ "command": "cmd", "args": ["/c", "npx", "-y", "figme-mcp"] }

Claude Code

claude mcp add figme -- npx -y figme-mcp           # this project
claude mcp add -s user figme -- npx -y figme-mcp   # every project

Or commit a .mcp.json at the repository root so collaborators get it too:

{
  "mcpServers": {
    "figme": {
      "command": "npx",
      "args": ["-y", "figme-mcp"]
    }
  }
}

Shortened. The full README is on GitHub.