figma-mcp-express
Enhanced fork of vkhanhqui/figma-mcp-go.
Fast, quota-free, agent-ready Figma MCP. Give AI agents direct read/write access to Figma through a local Desktop plugin, with batch execution, multi-file routing, and stable concurrent sessions that are not capped by Figma's official MCP server tool-call limits.
Claude Code, Codex, and other coding agents that can use the local filesystem is recommended. Unlike cloud-only MCPs, figma-mcp-express uses the filesystem to optimize the performance and stability.
If you are building design migration, audit, or handoff agents, give it a try.
| Promise | What it means in practice |
|---|
| Fast | Build with fewer LLM ↔ plugin round-trips by batching dependent operations into one call. |
| Quota-free | Plugin-side work is not capped by Figma's official MCP server limits, such as 6 calls/month for View/Collab seats or 200-600 calls/day for Dev/Full seats. |
| Agent-ready | Multiple agents can share a compact default tool surface safely through channel routing, reconnects, read dedup, and a hardened request queue. |
Why this fork exists
| Compared with | What blocks real automation | What figma-mcp-express adds |
|---|
| Official Figma MCP | Seat-based MCP server limits: View/Collab seats get up to 6 calls/month, while Dev/Full seats get daily and per-minute caps. | Local plugin-side read/write access for open files without those official MCP tool-call quotas. |
| Plain figma-mcp-go | Single-connection assumptions, no batching, no parallel agents, weaker library automation, and reconnect flapping under multi-file or long-running sessions. | Multi-file channels, batch ops, library tooling, response spill-to-disk, reconnect safety, and concurrent agent handling. |
| Manual Figma cleanup | Repetitive token binding, component replacement, audits, and design-to-code extraction. | Agent workflows that can scan, modify, verify, and report across large files. |
Who this is for
- Coding agents (Claude Code, Codex) — the primary target. Skills ship with the server and load from the local filesystem, so the agent has structured guidance without burning context on docs. Spill-to-disk keeps large Figma reads out of the context window entirely.
- Design systems teams migrating products to a new component library or token system
- Product designers cleaning up large production files without doing every replacement by hand
- Frontend engineers who need better design-to-code context than screenshots and comments
- Teams experimenting with multi-agent workflows for audits, migrations, and handoff generation
Before / After
