Windows: Chroma MCP connection fails with uvx.cmd - use uvx instead

[ChanghoSong]

Bug Description

On Windows (Git Bash / MSYS2 environment), ChromaMcpManager fails to connect to chroma-mcp via StdioClientTransport because it uses uvx.cmd instead of uvx.

Error

[CHROMA_MCP] Connecting to chroma-mcp via MCP stdio {command=uvx.cmd, args=chroma-mcp --client-type persistent --data-dir C:\Users\...\.claude-mem\chroma}
[CHROMA_MCP] Connection failed, killing subprocess to prevent zombie {error=MCP error -32000: Connection closed}

Root Cause

In src/services/sync/ChromaMcpManager.ts line 106:

const uvxCommand = isWindows ? 'uvx.cmd' : 'uvx';

StdioClientTransport from @modelcontextprotocol/sdk uses child_process.spawn() internally without shell: true. On Windows, spawning .cmd files via spawn() without shell: true can cause immediate process termination / connection closed errors.

Fix

Change uvx.cmd to uvx. The uvx binary is directly executable in Git Bash / MSYS2 environments without the .cmd wrapper:

const uvxCommand = isWindows ? 'uvx' : 'uvx';
// or simply:
const uvxCommand = 'uvx';

Workaround

Patch the built file directly:

sed -i 's/"uvx.cmd"/"uvx"/g' ~/.claude/plugins/cache/thedotmack/claude-mem/<version>/scripts/worker-service.cjs
# Restart worker after patching

Note: This patch is lost on /plugin update claude-mem.

Environment

• Windows 10 Pro 10.0.19045
• Shell: Git Bash (MSYS2)
• uvx 0.10.0
• chroma-mcp 1.6.0 (via uvx)
• claude-mem v10.3.1
• Node.js with @modelcontextprotocol/sdk StdioClientTransport

Verification

After patching uvx.cmd → uvx, Chroma connects successfully:

[CHROMA_MCP] Connected to chroma-mcp successfully
[CHROMA_SYNC] Backfilling observations {project=.claude, missing=1032, existing=0, total=1032}

[github-actions]

The issue reports a bug where ChromaMcpManager fails to connect to chroma-mcp in Windows environments using Git Bash or MSYS2. This occurs because the code incorrectly uses uvx.cmd instead of uvx for Windows. The problem arises since StdioClientTransport leverages child_process.spawn() without shell: true, which cannot handle .cmd file execution properly on Windows, leading to immediate process termination. The proposed fix is to change the command from uvx.cmd to uvx, as the latter works without the .cmd wrapper in these environments. A workaround to manually patch the built file is also provided, though updates overwrite it. The bug affects environments using frameworks like Node.js with @modelcontextprotocol/sdk and tools like claude-mem, but after applying the fix, the connection to chroma-mcp is established successfully.

[thedotmack]

Closed via v10.4.0 release — fixed in PR #1214.