mcp-wsl-setup

Fix VS Code MCP server stdio launches when running Node/pnpm inside WSL via fnm.

pnpm dlx mcp-wsl-setup

Or with npx:

npx mcp-wsl-setup

Run from your WSL terminal. The script auto-detects your fnm/pnpm paths and rewrites your VS Code user mcp.json in place. Reload the VS Code window afterwards (Ctrl+Shift+P → Developer: Reload Window).

Copy .vscode/tasks.json into your project. Then Ctrl+Shift+P → Tasks: Run Task → Fix MCP pnpm path runs pnpm dlx mcp-wsl-setup without leaving the editor.

---

How to run VS Code MCP servers (stdio transport) reliably when your development environment is WSL but VS Code is a Windows host application.

---

1. Environment Overview
2. fnm and Node.js Setup
3. Shell Configuration
4. The Problem
5. Root Causes — In Order of Discovery
6. The Solution
7. Final Working Configuration
8. The `resolve-pnpm.js` Script
9. VS Code Task
10. Replicating This Setup
11. Troubleshooting Reference

---

| Component | Detail | |-------------------|---------------------------------------------------------------| | Host OS | Windows 11 | | Linux environment | WSL 2 (Ubuntu) — distro name in WSL_DISTRO_NAME | | Node manager | fnm installed inside WSL | | Node.js | ~/.local/share/fnm/aliases/default/bin/node | | Package manager | pnpm, bootstrapped via corepack (bundled with