mcp-cross-environment-mc-mcp-server-fails-to-install-tools-and-shows-client-35084be7

THEN Ensure the MCP server command and working directory are fully within the target environment (e.g., WSL2). For WSL2 projects, run Cursor inside WSL2 using the Remote-WSL extension so that MCP commands execute natively in Linux. If not possible, configure the MCP command to use a WSL bridge such as 'wsl.exe -- bun /path/to/server.ts' and ensure bun is installed in WSL2.

// Instead of using a native Windows command, wrap the server invocation in a shell script that runs inside WSL2:
// .cursor/mcp.json
{
  "mcpServers": {
    "TalkToFigma": {
      "command": "wsl.exe",
      "args": ["bun", "/home/user/project/server.ts"]
    }
  }
}