Window mcp instalation repo path needs double slashes

[rodev018]

Describe the bug
When configuring mcpServers on Windows, paths containing backslashes are not handled correctly if not escaped in JSON. Using a path like c:\temp\bvb causes MCP error -32000: Connection closed because \t is interpreted as a tab character.

To Reproduce
Steps to reproduce the behavior:

Create an MCP configuration on Windows similar to:

json
Copy
Edit
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"mcp-server-git",
"--repository",
"c:\temp\project"
]
}
}
}
Start KiloCode in VS Code.

Observe that the MCP connection fails with error -32000: Connection closed.

Expected behavior
The MCP server should connect successfully when given a valid Windows path, even if the path uses standard backslashes (as is default in Windows).

Logs

nginx
Copy
Edit
MCP error -32000: Connection closed
Additional context
Escaping the Windows path (e.g., "C:\temp\project") fixes the issue. This may need better documentation, automatic escaping, or clearer error messaging to prevent confusion for Windows users.