modelcontextprotocol
Bug Report: Windows Path Parsing Error in commend parameters
Inspector Version
0.17.0
Describe the bug
In Windows environments, the inspector incorrectly parses Windows file paths in command parameters. Backslashes in paths are not properly escaped, causing path resolution errors.
To Reproduce
Steps to reproduce the behavior:
- Run the command with a Windows path containing backslashes in a Windows environment
- Execute:
npx @modelcontextprotocol/inspector java -Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=4000,suspend=n -jar C:\Users\username\project\target\app.jar - Observe path parsing error
- See the failure to locate the jar file
Expected behavior
The inspector should correctly handle and parse Windows paths with backslashes, either by automatically escaping them or properly interpreting native Windows paths.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
- OS: Windows
- Browser: N/A (command line tool)
Additional context
The issue can be temporarily resolved by manually escaping backslashes in paths (using double backslashes \\), but this should be handled automatically by the inspector.
Corrected command example:
npx @modelcontextprotocol/inspector java -Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=4000,suspend=n -jar C:\\Users\\username\\project\\target\\app.jar
