fix: Cursor MCP tools not showing (silence dotenv stdout)#9
Merged
Conversation
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
1 participant
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
Fixes Cursor MCP integration where tools do not appear even though the server starts successfully.
Root Cause
dotenv@17prints startup text to stdout by default:MCP stdio transport requires stdout to contain only MCP protocol messages. Any extra text corrupts the protocol stream and Cursor fails to detect tools.
Changes
config()→config({ quiet: true })insrc/index.tsContext
This addresses Issue #7 (
Does not work with Cursor Editor) and ports the relevant fix discovered inlaststance/electron-mcp-server.Closes #7