Fix: MCP stdio transport broken by non-JSON startup output on stdout - #63
Open
disq wants to merge 1 commit into
Open
Fix: MCP stdio transport broken by non-JSON startup output on stdout#63disq wants to merge 1 commit into
disq wants to merge 1 commit into
Conversation
Run tsx directly instead of via npm start (npm echoes the script to stdout), and pass quiet: true to dotenv so its injection banner is suppressed. MCP clients require stdout to carry only JSON-RPC.
disq
marked this pull request as ready for review
August 19, 2026 13:11
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.
Issue
The Docker image writes non-JSON output to stdout on startup, so MCP clients on the stdio transport fail to parse it ("Unexpected token" errors in Claude Desktop). Two sources:
npm startechoes the script command, and dotenv v17 prints its injection banner.Solution
npx tsx src/cli.tsdirectly, bypassing npm's echo.NPM_CONFIG_UPDATE_NOTIFIER=falsesilences the npx update notice.dotenv.config()getsquiet: true.npm start.QA
initializerequest throughdocker run -i: stdout carries only the JSON-RPC response, stderr is empty.