Fix: Use absolute path to uv executable in Claude Desktop config #440
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
When users run mcp install server.py, the CLI adds a configuration to Claude Desktop that uses just "uv" as the command instead of the full path. This causes Claude Desktop to fail when it can't find uv in its PATH environment, leading to errors and wasted developer time debugging configuration issues. This problem is particularly difficult for new users who might not understand why Claude Desktop can't find the uv command.
How Has This Been Tested?
Added a new unit test 'test_absolute_uv_path' that specifically verifies the absolute path to uv is used in the Claude Desktop configuration.
Existing test 'test_command_execution' continues to pass with the changes.
Manually tested with Claude Desktop on macOS to verify the configuration works correctly.
Confirmed that all existing tests continue to pass with the change.
Breaking Changes
None. This change is fully backward compatible and only improves reliability.
Types of changes
Checklist
Additional context