WSL Support/Configuration

[dsebastien]

I run Dockmaster on Windows, next to Claude Desktop. That works great.
Now, I'd like to reuse the MCP Servers I have installed/configured in Dockmaster with Claude Code, which I have installed within WSL.

To start Claude Code, I can use claude --mcp-config /c/Users/foo/AppData/Roaming/Claude/claude_desktop_config.json so that Claude Code knows about the MCP servers that have been configured for Claude. That more or less "works". I have to do that because the claude mcp add-from-claude-desktop command does not work in my case.

Unfortunately, Claude Code fails to connect to the Dockmaster "proxy", which seems logical given the way it's configured:

"mcp-dockmaster": {
      "args": [],
      "command": "\\\\?\\C:\\Users\\trankill\\AppData\\Local\\MCP Dockmaster\\mcp-proxy-server.exe"
    },

The errors I get with the above:

[DEBUG] MCP server "mcp-dockmaster": Connection failed: Error: spawn \\?\C:\Users\foo\AppData\Local\MCP Dockmaster\mcp-proxy-server.exe ENOENT
[DEBUG] MCP server "mcp-dockmaster": Error message: spawn \\?\C:\Users\foo\AppData\Local\MCP Dockmaster\mcp-proxy-server.exe ENOENT
[DEBUG] MCP server "mcp-dockmaster": Error stack: Error: spawn \\?\C:\Users\foo\AppData\Local\MCP Dockmaster\mcp-proxy-server.exe ENOENT
    at __node_internal_captureLargerStackTrace (node:internal/errors:563:5)
    at __node_internal_errnoException (node:internal/errors:690:12)
    at ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Nothing surprising really, since Claude Code running in WSL does not appreciate that path. I've worked around this by adding the Dockmaster MCP server manually in Claude Code using claude mcp add dockmaster /c/Users/foo/AppData/Local/MCP\ Dockmaster/mcp-proxy-server.exe

It would be great if the necessary Claude Code config could be added directly from Dockmaster's "Home" screen.