figma-vault MCP server

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.

however many times the agent looks.

• 3 Figma requests per screen, spent once when you pull it. After that it's zero,

• 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.

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:

reads it from git. Nobody else needs Figma access.

• The vault is meant to be committed. One person pulls a design and the whole team

built locally. Rendering them through Figma would eat the image-render limit.

• Icons cost zero requests. Vector paths come with the node tree, and the SVGs are

and a strict validator checks every file.

• The format is fixed and validated. doc.json follows a written contract,

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"

Shortened. The full README is on GitHub.