Describe the bug
When adding an MCP server from the CLI, you get a nice TUI to define the info for the server. However, if you put something into "Command" with backslashes (i.e. dotnet run --project D:\projects\terminal\src\tools\wt.mcp), the backslashes don't automatically get escaped! This results in the MCP server not working!
When you later check the MCP server configuration, it will remove the \ so it ends up looking like this: dotnet run --project D:projectsterminalsrctoolswt.mcp.
Affected version
No response
Steps to reproduce the behavior
/mcpa to add a new server- fill out the details; in
Command use something with backslashes (see example above)
- save
The MCP server fails to work. The error doesn't have anything to do with backslashes either! (which is expected tbh, but it made tracking this down a bit harder)
Expected behavior
Given that it's a TUI, there should not be a need to escape characters or backslashes.
Additional context
No response
Describe the bug
When adding an MCP server from the CLI, you get a nice TUI to define the info for the server. However, if you put something into "Command" with backslashes (i.e.
dotnet run --project D:\projects\terminal\src\tools\wt.mcp), the backslashes don't automatically get escaped! This results in the MCP server not working!When you later check the MCP server configuration, it will remove the
\so it ends up looking like this:dotnet run --project D:projectsterminalsrctoolswt.mcp.Affected version
No response
Steps to reproduce the behavior
/mcpato add a new serverCommanduse something with backslashes (see example above)The MCP server fails to work. The error doesn't have anything to do with backslashes either! (which is expected tbh, but it made tracking this down a bit harder)
Expected behavior
Given that it's a TUI, there should not be a need to escape characters or backslashes.
Additional context
No response