Description

Fixes #4933

This PR fixes an issue where MCP server paths containing ampersands (&) would fail to launch on Windows. The problem occurred because the command was wrapped with cmd.exe /c without properly quoting the path, causing cmd.exe to interpret the ampersand as a command separator.

Changes Made

• Modified src/services/mcp/McpHub.ts to quote the command path when wrapping with cmd.exe on Windows
• Updated test expectations in src/services/mcp/__tests__/McpHub.spec.ts to reflect the new quoted command format
• Added a new test case specifically for verifying that paths with ampersands are properly handled

Testing

• All existing tests pass
• Added test for paths containing ampersands: should properly quote commands with special characters like ampersand
• Manual testing completed:
  • Verified that MCP servers with & in their path can now be launched on Windows
  • Confirmed that servers without special characters continue to work as expected

Verification of Acceptance Criteria

• MCP servers with & in their file path now connect successfully on Windows
• The fix is applied only on Windows platforms (non-Windows behavior unchanged)
• Commands that are already wrapped with cmd.exe are not double-wrapped
• All existing functionality remains intact

Checklist

• Code follows project style guidelines
• Self-review completed
• Comments added for complex logic
• Documentation updated (if needed)
• No breaking changes
• Tests added for the fix

Technical Details

The fix works by wrapping the command in quotes when passing it to cmd.exe:

// Before
['/c', configInjected.command, ...(configInjected.args || [])]

// After  
['/c', `"${configInjected.command}"`, ...(configInjected.args || [])]

This ensures that cmd.exe treats the entire path as a single argument, preventing special characters like & from being misinterpreted.