figma-export-mcp
An MCP server bulk-exports images from Figma and uploads the verified result to Yandex Disk, with a confirmed plan before any upload
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Uploads files to the user's Yandex Disk, requiring a token with write rights
- Figma and Yandex Disk tokens are passed through process environment variables
Install
Manual install
npm ci
npm run check
npm run build
FIGMA_TOKEN=... YANDEX_DISK_TOKEN=... npm startInstall, check and run the server, from the README.
This is third-party code. Review the repository files before installing.
What it does
The server parses an arbitrarily organized Figma file and builds an export plan: which nodes, in which formats and under which names become files and ZIP archives, shows a preview with paths and asks for confirmation by the plan's digest before downloading anything. Once confirmed, it bulk-exports images via the Figma REST API, packages them with streaming ZIP64 so memory does not grow with archive size, and uploads the result to Yandex Disk through its REST API. Uploads resume via a retry_failed_items tool without resending already-verified files, and job state is stored atomically on disk.
Who it is for. For designers and product teams who regularly need to export large sets of icons or mockups from Figma to Yandex Disk.
Good fit when
- You need to bulk-export dozens or hundreds of Figma nodes with selection and naming rules
- You want the result delivered straight to Yandex Disk without a manual upload
- The export is on a flaky network and you need uploads to resume without resending already-sent files
Not a fit when
- You need to export to a different cloud storage: the server is purpose-built for Yandex Disk only
- You need to modify the Figma file itself: the server only reads and exports, it never touches the design
Example request
Export all icons from the Icons page in Figma to SVG and upload them to Yandex Disk into the icons folderLimitations
It requires Figma and Yandex Disk tokens. It uses a Figma personal access token by default; an OAuth token needs FIGMA_AUTH_MODE=oauth set explicitly. The package ships only as a tarball inside the repo, not published to npm. The repository was originally framed as a task brief for autonomous Codex development, and part of the README covers that process, but the repo holds a finished implementation with tests and CI.
How to disable. Remove the server from your MCP client config and revoke the Figma and Yandex Disk tokens in the respective account settings.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| FIGMA_TOKEN required, secret | Figma personal access token, used by default in pat mode |
| FIGMA_AUTH_MODE | Figma auth mode: pat by default or oauth |
| FIGMA_OAUTH_ACCESS_TOKEN secret | Figma OAuth access token when FIGMA_AUTH_MODE=oauth |
| YANDEX_DISK_TOKEN required, secret | Yandex Disk access token for uploading exported files |
| FIGMA_EXPORT_MAX_TEMP_BYTES | Temp-disk limit while streaming the ZIP64 build |
Security check
- Uploads files to the user's Yandex Disk, requiring a token with write rights
- Figma and Yandex Disk tokens are passed through process environment variables
README in short
The README frames the repository as a task brief for autonomous Codex, but the directory holds a finished STDIO MCP server on Node.js 20+. It covers install and run commands, environment variables for Figma and Yandex Disk, PAT and OAuth auth modes, behavior on 429 and 5xx errors, a temp-disk limit for ZIP64, and an optional live-smoke script for a read-only check that uploads nothing. Separate documents cover the architecture, the export plan schema, Figma node selection rules and the Yandex Disk delivery protocol.
FAQ
Does the server upload files right after the request?
No, it first builds an export plan with a path preview, and upload starts only after confirming the plan's digest.
What happens if the Yandex Disk upload breaks halfway?
The retry_failed_items tool resumes the upload and does not resend files that already passed verification.
Related
Official Claude Code plugin from the Next.js repo: adopting Cache Components and Partial Prefetching, and verifying changes on a running dev server
Official shadcn/ui skill and MCP server: the agent searches registries, adds components via the CLI and follows the library's rules
A frontend design skill with 23 commands, live browser iteration and 61 detector rules for common AI-generated UI tells
Vercel Agent Skills
Agent Skills
Vercel's skills: React and Next.js performance, UI guideline audits, React Native, component composition and deploys