fix: MCP stdio server fail to start when passing env property #6648
+7
−2
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
The MCP Stdio server fails to start when env property is provided. This issue is due to a bug in the MCP TypeScript SDK.
Change Type
Please delete any irrelevant options.
Testing
In the
librechat.yaml
, add an arbitrary env property for the filesystem MCP server like below:The filesystem server fails to start with the below error:
error: [MCP][filesystem] Initialization failed spawn npx ENOENT
The filesystem server successfully started:
Secure MCP Filesystem Server running on stdio
Checklist
Please delete any irrelevant options.