This post was generated by an AI agent from an article the account owner published in Japanese on note. The wording is not human-written.
Setting up Claude Code to control Figma over MCP sounded straightforward: Anthropic's AI coding tool can talk to external tools via MCP, and Figma has an MCP server. In one attempt to connect the two using only Figma's free plan (no Dev Mode), nearly every step hit a snag before it worked.
Environment
- OS: Windows 11
- Figma: Free plan (desktop app)
- Claude Code: Pro plan
- Node.js: v18.16.1
- Bun: v1.3.9 (installed partway through)
The core question going in was whether Figma integration was even possible without the paid Dev Mode feature.
Step 1: Read-only MCP, eventually
The official remote MCP was the first thing tried:
claude mcp add --transport http figma https://mcp.figma.com/mcp
The result:
figma: https://mcp.figma.com/mcp (HTTP) - ✗ Failed to connect
The official remote MCP requires OAuth authentication, which didn't work smoothly here.
Next, a community-made MCP, @rui.branco/figma-mcp, was tried instead. This one uses a Figma personal access token, generated from Figma's Settings > Account > Personal access tokens.
claude mcp add figma-mcp -e FIGMA_PERSONAL_ACCESS_TOKEN=your_token -- npx -y @rui.branco/figma-mcp
That also failed to connect at first. The error pointed to a missing config file:
Error: ENOENT: no such file or directory, open 'C:\Users\user\.config\figma-mcp\config.json'
A config file had to be created manually:
mkdir -p ~/.config/figma-mcp
{
"figmaToken": "your_token"
}
Saved to ~/.config/figma-mcp/config.json, after which the connection succeeded:
figma-mcp: npx -y @rui.branco/figma-mcp - ✓ Connected
This MCP is read-only, though — it can fetch Figma design data but can't create or edit designs.
Step 2: MCP for actually creating designs
The real target was claude-talk-to-figma-mcp, which lets the AI draw on the Figma canvas. The architecture:
Claude Code ←(MCP)→ MCP server ←(WebSocket)→ Figma plugin ←→ Figma
A WebSocket connection relays messages between Claude Code and a Figma plugin.
First, add the MCP server:
claude mcp add claude-talk-to-figma -- npx -p claude-talk-to-figma-mcp@latest claude-talk-to-figma-mcp-server
Then clone and build the repository, which is needed to run the WebSocket server:
git clone https://github.com/arinspunk/claude-talk-to-figma-mcp.git
cd claude-talk-to-figma-mcp
Installing dependencies required Bun, which wasn't installed yet:
npm install -g bun
bun install
Running bun run socket then failed with:
error: Module not found "dist/socket.js"
The project hadn't been built yet. Building it fixed that:
bun run build:win # for Windows
After the build succeeded, bun run socket worked:
[INFO] Claude to Figma WebSocket server running on port 3055
Step 3: The Figma plugin trap
Next, the plugin needed to be loaded into the Figma desktop app via Menu → Plugins → Development → Import plugin from manifest, pointing at:
claude-talk-to-figma-mcp/src/claude_mcp_plugin/manifest.json
After selecting the manifest, "Claude Talk to Figma MCP" didn't show up in the plugin menu at all.
The fix, found only through trial and error: close the plugin menu after importing the manifest, then reopen it. Only then does "Claude Talk to Figma MCP" appear in the list. Why this happens isn't clear — it appears to just be how Figma's plugin menu behaves — but roughly 30 minutes went into this before finding the workaround.
Step 4: Connection
Launching the plugin brings up a connection screen. Clicking "Connect" produced:
Connected on port 3055!
Copy the channel ID: g54uwzq5
That channel ID is then passed to Claude Code so it can control Figma:
Connect to Figma. Channel ID: g54uwzq5
Note: the channel ID changes every time the plugin is restarted.
Result
The end state is a working setup where Claude Code controls Figma, entirely on Figma's free plan. The whole process took about an hour, with several points of friction along the way. Once set up, however, reconnecting on future sessions just means starting the WebSocket server and reconnecting the plugin — no need to repeat the earlier troubleshooting.
Setup checklist
One-time setup:
- Generate a personal access token in Figma
- Set the token in
~/.config/figma-mcp/config.json - Add two MCP servers with
claude mcp add(one read-only, one for design creation) - Clone the
claude-talk-to-figma-mcprepository - Run
bun installandbun run build:win - Import the plugin into the Figma desktop app
Every session:
- Start the WebSocket server with
bun run socket - Launch the plugin in Figma and click "Connect"
- Pass the channel ID to Claude Code
Three main snags:
-
config.jsonisn't created automatically — it has to be made by hand - The project must be built with
bun run build:winbeforebun run socketwill work - The plugin doesn't appear in the menu until the plugin menu is closed and reopened once
Follow @kmrb_works here on DEV for more field notes from real development work. Also on X and note, mostly in Japanese.
Top comments (0)