REST API in the middle
- Personal access token setup
- Plan-dependent API limits
- Incomplete write workflows
- More translation between intent and canvas
Figma Go gives your AI agent read and write access to the live canvas—without a Figma API token or REST API rate limits.
npx -y @joefour/figma-go@latest setup --allOne commandReading the selected frame and its design system…
One bridge. Your choice of AI client.
Figma Go replaces a fragile, read-mostly API workflow with a direct bridge to the document you already have open.
Keep the conversation in your AI client while Figma remains the source of truth.
Install the MCP server and open the Figma Go plugin in your file.
Ask your agent to inspect, generate, or modify the selected design.
Carry the exact structure and design context into implementation.
From a first wireframe to a component system and production code, Figma Go keeps the workflow grounded in your live file.
Inspect frames, components, variables, styles, prototypes, and content directly from the open Figma file.
Turn intent into frames, components, imagery, responsive layouts, and polished visual systems.
Give your coding agent the structure and context it needs to implement the design with fewer guesses.
The plugin bridge works with the live document instead of consuming the Figma REST API quota.
No personal Figma API token is required. The bridge is available only while you have the plugin open.
Connect Codex, Claude, Cursor, GitHub Copilot, OpenCode, or another MCP-compatible client.
Start with the open-source server, connect your preferred client, and make the canvas part of the conversation.