Summary
Design edits that land in the file, not in a description of the file.
Most Figma MCP servers read through the REST API and are metered by your Figma plan. This one drives the app through a plugin, which is what makes writing — creating frames, setting text, importing images — a normal operation rather than a rationed one.
What it is
A Figma MCP server that works through a Figma plugin bridge instead of the REST API, so both reading and writing happen against the document you have open.
What you get
- Layout primitives created on the canvas: frames, rectangles, ellipses and sections
- Text placed as new layers, or written into layers that already exist
- Images imported into the file rather than described in a comment
- Components created from what you have built, so a repeated element becomes reusable
- A write path that does not spend Figma REST API tool calls — the plugin bridge is not subject to the per-plan REST quotas that meter API-based Figma servers, and those are tightest on a free Starter plan
Requirements
Npx @vkhanhqui/figma-mcp-go@latest — one line for Claude Code, Codex CLI or an .mcp.json entry, no build step. Figma must be open with the companion plugin running, since that bridge is how the server reaches the document. No Figma API token; a free Figma plan is enough.
Setup effort
One command — npx -y @vkhanhqui/figma-mcp-go