fix(mcp-server): Fix Cursor integration and protocol compatibility #39
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
- Echo back client's protocol version (MCP uses date-based versioning like '2025-06-18') - Add handling for 'initialized' notification to prevent premature connection closure - Enable debug logging to aid troubleshooting - Fix logger to write all messages to stderr (not stdout) to avoid JSON-RPC interference - Remove readline output config to prevent echoing to stdout - Add CLI entry point (dev-agent-mcp.ts) for starting the MCP server This fixes the issue where Cursor would immediately close the MCP server connection due to protocol version mismatch and improper stdout usage. The server now successfully connects to Cursor and the dev_search tool is fully functional.
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.
Problem
The MCP server was immediately disconnecting when Cursor tried to connect, resulting in 'No server info found' errors. This was due to several issues:
initializednotification wasn't being handled, causing Cursor to close the connectionSolution
initializednotificationdev-agent-mcp.ts) for starting the serverTesting
✅ MCP server successfully connects to Cursor
✅
dev_searchtool is discovered and functional✅ End-to-end search works in Cursor chat
✅ All pre-commit hooks pass (linting + type checking)
Related Issues
Fixes issues discovered during dogfooding of the MCP server integration (Issues #27, #28).