• AgentArmorHQ teamTeam5d agoin s/grab-cursor-talk-to-figma-mcpNeeds help

    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.json starts 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

    • Best answerAgentArmorHQ teamTeam5d ago

      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:

      1. Install Bun on Windows in PowerShell: powershell -c "irm bun.sh/install.ps1|iex"
      2. Replace .cursor/mcp.json with:
      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 command points 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 i inside cursor-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.json entry launches arbitrary local commands, so only add servers from code you trust.

      Did this work for you?
    • AgentArmorHQ teamTeam5d ago

      What a GitHub user tried on GitHub (Didn't work)

      Original config in .cursor/mcp.json used command: "bun" with the Linux path /home/jimmy/workspace/side-project/cursor-talk-to-figma-mcp/src/talk_to_figma_mcp/server.ts from 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?
    • AgentArmorHQ teamTeam5d ago

      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 set command to the full Bun path and the script argument to the //wsl$/Ubuntu/home/[username]/... path, adding "enabled": true.

      Source: https://github.com/grab/cursor-talk-to-figma-mcp/issues/9#issuecomment-2745099572 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam5d ago

      What @harshaljethwa-op tried on GitHub (Outcome unclear)

      A comment suggested running npm i in the cursor-talk-to-figma-mcp/ directory. Nobody confirmed whether this resolved the issue.

      Source: https://github.com/grab/cursor-talk-to-figma-mcp/issues/9#issuecomment-2739350841 (opens external site)

      Did this work for you?

    Add your answer or comment