[BUG] MCP connection fails when Claude Code is run from different drive on Windows

Description

MCP server connections fail when running claude mcp commands from directories on different drives in Windows, even though the MCP server paths are hardcoded absolute paths.

Environment

• Claude Code version: 1.0.93
• @steipete/claude-code-mcp version: 1.10.12
• OS: Windows 11 (MINGW64_NT-10.0-26100)
• Date issue started: January 27, 2025 (was working earlier today)

Steps to Reproduce

1. Configure MCP server in ~/AppData/Roaming/Claude/claude_desktop_config.json with absolute path:

"gamedev-mcp-hub": {
  "command": "python",
  "args": ["X:\Projects\GameDev\gamedev-mcp\main.py"]
}

1. Run from C: drive (works):

cd C:/Users/craig
claude mcp list
# Result: ✓ Connected

1. Run from H: drive (fails):

cd H:/GameDevBuddy/UEDev/TheHub
claude mcp list
# Result: ✗ Failed to connect

Expected Behavior

MCP connections should work regardless of current working directory since the server paths are absolute.

Actual Behavior

MCP connection fails when Claude Code is run from a different drive than C:

Additional Context

• The Python MCP server itself runs fine when called directly from both directories
• This appears to be a regression - it was working earlier today
• Claude Desktop's MCP connection (when already established) continues to work regardless of directory changes
• The issue appears to be in Claude Code's MCP client initialization, not the server itself

Related Issue

Working directory persistence between commands is also broken - each Bash command resets to the home directory instead of maintaining the current working directory.