Add common issue to find uv/uvx to Troubleshooting

[dsp-ant]

We need to improve the documentation to avoid people getting caughitn with uv/uvx not found. See modelcontextprotocol/servers#37

[alexfinnarn]

I came here and found this issue after having to use a full path to npx since I use asdf with zsh and thought Claude Desktop might be choking on figuring out where npx lives even though my terminal app loads the paths correctly.

I think adding more notes to https://github.com/modelcontextprotocol/docs/blob/main/docs/tools/debugging.mdx#working-directory makes sense. I can take a stab at creating a PR that would add a bullet point like:

"Use full paths for commands. Even though your favorite terminal application might have a custom configuration for loading paths, Calude Desktop might not know this. Run which npx in your terminal and use that output for the command."

I too did not see much in the logs and just had a hunch Claude Desktop could not find npx. All I had was command not found: /Users/alexfinnarn/Desktop to go off of in my logs.

Full log sequence:

"2025-03-23T01:43:07.833Z [filesystem] [info] Server started and connected successfully
2025-03-23T01:43:07.862Z [filesystem] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
command not found: /Users/alexfinnarn/Desktop
2025-03-23T01:43:08.100Z [filesystem] [info] Server transport closed
2025-03-23T01:43:08.100Z [filesystem] [info] Client transport closed
2025-03-23T01:43:08.100Z [filesystem] [info] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. console.error('...') in JavaScript, print('...', file=sys.stderr) in python) and it will appear in this log.
2025-03-23T01:43:08.100Z [filesystem] [error] Server disconnected. For troubleshooting guidance, please visit our [debugging documentation](https://modelcontextprotocol.io/docs/tools/debugging) {"context":"connection"}
2025-03-23T01:43:08.101Z [filesystem] [info] Client transport closed"

[alexfinnarn]

#233 is my attempt to help users avoid issues with executables not being found. They might report various errors in logs, like mine, which was related to argument order, but this should clear up a whole slew of errors with incorrect command configuration.

I decided to put it in the actual quickstart since I did not get the same error as the one in modelcontextprotocol/servers#37 and I'm not sure how to word this in troubleshooting...not really working directory-related but maybe needs creating a new section.