Talk-to-Figma MCP "Client closed" on Cursor Windows + WSL2: how to fix?
cursor-talk-to-figma-mcp shows "No tools available" and a red "Client closed" error in Cursor on Windows 10 when the project lives in WSL2 (Ubuntu). My
.cursor/mcp.jsonstarts Bun with the Linux path/home/jimmy/.../server.ts. How do I get the MCP working across Windows and WSL2?Originally asked on GitHub: https://github.com/grab/cursor-talk-to-figma-mcp/issues/9
4 answers
Status: a contributor posted a Windows + WSL2 fix that was confirmed working; the thread does not officially confirm the root cause, and the same error on macOS got no fix.
What worked:
- Install Bun on Windows in PowerShell:
powershell -c "irm bun.sh/install.ps1|iex" - Replace
.cursor/mcp.jsonwith:
json{ "mcpServers": { "TalkToFigma": { "command": "/Users/[username]/.bun/bin/bun", "args": [ "//wsl$/Ubuntu/home/[username]/path/to/cursor-talk-to-figma-mcp/src/talk_to_figma_mcp/server.ts" ], "enabled": true } } }Substitute your actual username and repo path. Compared with the original config, the
commandpoints to the Bun installed on Windows and the script argument uses the//wsl$/Ubuntu/...path form. As general advice: the Windows-side Cursor process resolves both paths, so make sure both are reachable from Windows before testing.What the thread did not resolve:
- A comment suggested running
npm iinsidecursor-talk-to-figma-mcp/; nobody confirmed it fixes the error. - Several macOS users reported the identical red "Client closed" with "No tools available"; the thread contains no Mac fix.
General advice: a project-level
mcp.jsonentry launches arbitrary local commands, so only add servers from code you trust.Did this work for you?- Install Bun on Windows in PowerShell:
What a GitHub user tried on GitHub (Didn't work)
Original config in
.cursor/mcp.jsonusedcommand: "bun"with the Linux path/home/jimmy/workspace/side-project/cursor-talk-to-figma-mcp/src/talk_to_figma_mcp/server.tsfrom Cursor on Windows. The MCP panel showed "No tools available" and a red "Client closed" error.Source: https://github.com/grab/cursor-talk-to-figma-mcp/issues/9 (opens external site)
Did this work for you?What @sonnylazuardi tried on GitHub (Worked)
Contributor's fix, confirmed working on Windows with a screenshot: install Bun via
powershell -c "irm bun.sh/install.ps1|iex", then setcommandto the full Bun path and the script argument to the//wsl$/Ubuntu/home/[username]/...path, adding"enabled": true.Did this work for you?What @harshaljethwa-op tried on GitHub (Outcome unclear)
A comment suggested running
npm iin thecursor-talk-to-figma-mcp/directory. Nobody confirmed whether this resolved the issue.Did this work for you?
Related questions
- cursor-talk-to-figma-mcp: 'Unexpected token C, "Connecting"... is not valid JSON' error
- How to fix "Client closed" / "Sending message to client: undefined" in cursor-talk-to-figma-mcp?
- cursor-talk-to-figma-mcp stuck at "joining channel" in Cursor?
- Cursor MCP shows "Client closed" and "No tools available" — how to fix?
- Figma Desktop shows "0 tools enabled" when connecting to a remote MCP server via port forwarding?