figma-vault

Name: figma-vault
Author: NBhey

by NBheyversion 0.1.5i★ –iRuns on your computer

Registry nameio.github.NBhey/figma-vault

Install

Overview

Description from the maker (original English)

Figma designs pulled once into a local vault; AI agents read them offline with no rate limits

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Design, images & audio

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add figma-vault -- npx -y figma-vault mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "figma-vault": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "figma-vault",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account NBhey, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Design, images & audioi

More stars than 0% of the other 2204 servers in this category
Published to the registry more recently than 40% of the other 2204 servers in this category
Basic checks equal to or better than 100% of the other 2204 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is figma-vault safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.5) reached the registry 40 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Figma Context MCP

by GLips

Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.

Runs on your computer★ 16,165MITUpdated 5 months ago

Install

Claude Real Video

by HUANGCHIHHUNGLeo

Let any LLM watch a video locally — and search everything it has ever watched.

Runs on your computer★ 2,284MITUpdated 2 months ago

Install

Figma MCP Server

by figma

Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.

Runs in the cloud★ 2,152Updated 13 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

figma-vault

English · Русский

Pull a Figma frame once. Then Claude Code, Codex or any MCP agent reads it as often as it likes: offline, with no Figma token and no rate limits.

Batch Figma requests once, then zero requests however many times the agent looks. Screens from one file share the structure read and image render batches.
Icons cost nothing. A real screen had 141 icons, and they took no extra requests.
Commit the vault and the team needs no Figma access. No licence, no token.

Try it in 30 seconds. You don't need a Figma token for this:

npm i -g figma-vault

figma-vault init && figma-vault demo && figma-vault check

How it works: the pull normalizes the frame and writes it to disk. The agent then reads it over MCP.

one developer:      figma-vault add <link>  →  vault  →  git commit

the rest of the team: the agent reads it over MCP, no Figma token needed

The problem

Figma's MCP server and REST API are rate-limited, and on some seats the limit is tiny. While building a UI, an agent goes back to the design all the time to check a margin, a colour or a font size. That can mean dozens of calls in one session. You hit the limit fast and the work stops.

With figma-vault, the number of Figma calls doesn't depend on what the agent does. Each design costs a fixed number of calls, spent once when you pull it.

	Figma Dev Mode MCP	figma-vault
who calls Figma	the agent, while it works	the CLI, once
how many calls	grows with the agent's work	fixed per design
does every reader need a token	yes	no
works offline	no	yes

There's a side effect: the design becomes a file in your repository. A developer without access to the Figma file (no licence, no permissions, no token) still gets the whole design.

How it compares

Other projects work on the same problem. The Framelink Exporter plugin exports a design to a zip for offline use, and there are caching forks of Framelink's Figma MCP. figma-vault takes a different approach:

The vault is meant to be committed. One person pulls a design and the whole team reads it from git. Nobody else needs Figma access.
Icons cost zero requests. Vector paths come with the node tree, and the SVGs are built locally. Rendering them through Figma would eat the image-render limit.
The format is fixed and validated. doc.json follows a written contract, and a strict validator checks every file.

Install

Requires Node.js 22+.

npm i -g figma-vault

Option 1. Per project

figma-vault init

This creates .figma-vault/, registers the server in the project's .mcp.json (other entries are left alone), adds .env to .gitignore and installs a /figma slash command for Claude Code.

Use --no-command to skip the /figma command, so the agent gets only the read-only vault_* tools.

Option 2. Nothing in the repository

figma-vault init --global

The vault lives in ~/.figma-vault/ and the server is registered in the agent's user config. The project repository never learns the tool exists. Use this when you can't add config or dependencies to the project.

Usage

figma-vault add "https://figma.com/design/KEY/Project?node-id=127-4532"

Export several selections together; links from the same file share requests:

figma-vault add " " " "

Keep the node trees if image rendering is unavailable:

figma-vault add " " " " --no-assets

A SECTION/CANVAS link can expand into its frames (up to 20 by default):

figma-vault add " " --expand --max-screens 20

To get the link, right-click a frame in Figma and choose Copy link to selection.

figma-vault limits "<frame link 1>" "<frame link 2>" # probe access before pulling

figma-vault list # what has been pulled so far figma-vault check # verify the whole chain works figma-vault demo # add a demo design, no token needed

CLI output, errors and the MCP tool descriptions are in English by default; the /figma command it installs is in English too. README.ru.md is a translation of the documentation only.

After init, Claude Code has one command:

/figma <frame link> [more frame links...]

It pulls the design, reads it over MCP and builds the UI following the project's conventions.

What a pull costs in Figma requests

REST API limits depend on the token, plan and seat type. Both node reads and image renders are Tier 1 endpoints. figma-vault limits " " [more links...] spends one shallow node read plus up to ceil(S/40) screen render requests per file. It skips rendering SECTION and CANVAS selections as whole images; their child screens are not probed. A successful probe cannot guarantee the full pull: asset renders can require additional requests.

For a file with S selected screens and R unique raster assets, when each screen has fewer than 40 raster assets, a successful pull typically uses:

	requests
selected node trees (`/v1/files/:key/nodes`)	1 per file
screenshots and raster assets (`/v1/images`, batches of 40 IDs)	`ceil((S + R) / 40)` per file
icons with local geometry	0

For example, two screens in one file with three unique raster assets take one node read and one image render if the five IDs fit in a batch. At 40 or more raster assets on one screen, screenshots are rendered separately. --expand first probes containers with depth=1, adding at least one node request per file. SVG fallback renders, failed requests and retries can add calls. On a real 332-node design, 141 icons needed no render calls. After the pull, the agent never calls Figma again.

Check the result against the design

figma-vault verify compares the page the agent built with the design. The package ships no browser: the snapshot is taken with whatever the project already uses (Playwright, DevTools, the agent's browser tool).

Mark the root element of the page with data-figma-node-id=" ", and the main blocks with the ids of their nodes.
figma-vault verify --snippet prints a script. Run it on the page and save what it returns to a file.
figma-vault verify --snapshot checks it:

texts: every visible text of the design must be on the page;
geometry: each marked block must match the design's position and size, within 2 px by default (--tolerance).

The result is PASS (exit code 0), FAIL (1, with a list of what is off) or INCOMPLETE (2, when nothing is marked and geometry can't be checked). The /figma command runs this step itself when the project has a browser.

Try it without a Figma token

You only need a token to pull new designs. Reading works without one, which is the normal setup for everyone except the person who pulls. So you can test the whole install without creating a token:

figma-vault init && figma-vault demo && figma-vault check

check starts the real MCP server as a child process and talks to it over the protocol. It exits with code 1 when something is actually broken, so you can use it in CI.

Token

In Figma, go to Settings → Security → Personal access tokens → Generate new token. The token needs only one scope: File content → Read-only.

Put it in a .env file in the directory you run the CLI from, as a line FIGMA_TOKEN=figd_..., or set it as an environment variable. If both are set, the environment variable wins.

What the agent gets

The MCP server exposes six read-only tools:

tool	returns
`vault_list`	the designs in the vault
`vault_get_doc`	a design's node tree; `maxDepth` limits the depth
`vault_get_node`	the subtree of one node
`vault_search`	nodes found by name or text
`vault_get_tokens`	colours, typography, effects
`vault_get_asset`	an image or an icon

The tree is normalized:

auto-layout becomes mode: row|column with gap and padding;
coordinates are relative to the parent;
styles, gradients and text come in one predictable shape, including differently coloured fragments inside one text (text.runs);
nodes hidden in Figma are kept with hidden: true. By default the agent doesn't get them, but a parent reports how many it has (hiddenOmitted). Pass includeHidden: true when building a reusable component whose optional slots are switched off on this screen.

The raw Figma response is saved next to it in raw.json for debugging.

On a real design, normalization shrinks the tree about 7 times:

raw.json   1.9 MB   raw Figma response

doc.json 256 KB what the agent reads

This saves more than disk space. An agent that reads 256 KB instead of 2 MB rebuilds the UI noticeably more accurately.

Vault layout

<vault>/

index.json list of designs / doc.json normalized tree, the main artifact raw.json raw Figma response screenshot.png render of the whole frame assets/ icons and images

The figma-vault/doc@1 schema is described in docs/CONTRACT.md (in Russian). A strict validator checks it. Vaults pulled with 0.1.0 (doc@0) are still read as they are; there is no need to pull them again.

doc.json stands on its own: the MCP server never reads raw.json and never touches the network.

Known limitations

This is an MVP. Here is what it can't do yet.

Rate limits. Node reads and image renders are both Tier 1. Either endpoint can return 429, and the block can last for days. Icons no longer depend on rendering, but the frame screenshot and raster images still do. The client retries up to three times, following Retry-After, and never sleeps for more than a minute. If Figma asks it to wait for days, the pull keeps the node tree, records the reason as a warning and doesn't fail. Run figma-vault limits before pulling.
Only colour and weight are kept for fragments inside a text. A gradient, a different font or an underline on part of a text is lost.
Designs with many component variants make a large `doc.json`. Hidden slots are kept now. On a 332-node screen that added 3,400 hidden nodes, and the file grew from 444 KB to 5 MB. The agent still gets about 100 KB by default, but the file goes into your git.

How it was tested

The fixture in the repository is synthetic: 29 nodes, enough to install the tool and confirm the chain works without a Figma token.

We checked accuracy separately, on two real designs whose content isn't published here. Results on a product screen with 332 nodes, 15 levels deep:

check	result
design texts present in the rebuilt markup	41 of 41
icons	15 of 15, 0 broken links
placeholders needed	1 (a raster avatar)
Figma requests in the earlier measured pull	3 (before combined rendering)
`doc.json` against the contract	passes

Not checked: pixel-perfect match. We compare with Figma's reference render by eye, using npm run dev → /compare/ . figma-vault verify checks texts and the geometry of marked blocks, but no

Only the beginning is shown; read the rest in the repo

figma-vault

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Design, images & audioi

Common questions

Alternatives

Figma Context MCP

Claude Real Video

Figma MCP Server

README from the maker

figma-vault

The problem

How it compares

Install

Option 1. Per project

Option 2. Nothing in the repository

Usage

Export several selections together; links from the same file share requests:

Keep the node trees if image rendering is unavailable:

A SECTION/CANVAS link can expand into its frames (up to 20 by default):

What a pull costs in Figma requests

Check the result against the design

Try it without a Figma token

Token

What the agent gets

Vault layout

Known limitations

How it was tested