feat: Add Support for Absolute Paths in MCP Server Configuration to Resolve NVM Issues (#64) #136
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.
Summary
This PR addresses Issue #64, which highlights a problem where MCP servers fail to work with Node Version Manager (NVM) due to incorrect Node version usage. The solution introduces the use of absolute paths for the Node executable and server script, ensuring compatibility in NVM environments. Additionally, documentation has been updated to guide users through this configuration.
Motivation and Context
When using NVM, the standard installation and usage instructions for MCP servers fail because the app attempts to use an incorrect Node version, leading to execution errors. This change:
How Has This Been Tested?
Breaking Changes
Yes, users must update their
config.json
to include absolute paths for the Node executable and server script. The updated documentation provides clear instructions for this transition.Types of changes
Checklist
Additional Context
Example Updated Configuration: