docs(memory): add WSL2 troubleshooting for npx stdout JSON parse errors#3804
Open
ssam18 wants to merge 1 commit intomodelcontextprotocol:mainfrom
Open
docs(memory): add WSL2 troubleshooting for npx stdout JSON parse errors#3804ssam18 wants to merge 1 commit intomodelcontextprotocol:mainfrom
ssam18 wants to merge 1 commit intomodelcontextprotocol:mainfrom
Conversation
…e errors Explains why `npx -y @modelcontextprotocol/server-memory` causes "Unexpected non-whitespace character after JSON at position 127" errors in WSL2, and provides two workarounds: global npm install and direct node invocation. Fixes modelcontextprotocol#3013.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Running the memory server via
npxin WSL2 causes JSON parse errors at a fixed byte offset because npx writes package resolution output to stdout, which corrupts the MCP stdio JSON-RPC stream. Added a troubleshooting section with two workarounds:nodeinvocationSo users can get unblocked without needing to dig through issues..