Fix MCP two-step handshake with proper 202 Accepted response
- Fixed notifications/initialized to return 202 Accepted instead of 204 No Content - Added comprehensive MCP method implementation (prompts, roots, sampling, etc.) - Enhanced notification handling with proper session state transitions - Updated protocol version support to include 2025-11-25 with backward compatibility - Improved error handling and logging for debugging MCP connections - Added subscription tracking and message storage for advanced features - Fixed Accept header validation per MCP 2025-11-25 specification Resolves the critical two-step handshake issue where MCP Inspector was not receiving the correct response for notifications/initialized.
Showing
3 changed files
with
187 additions
and
3 deletions
This diff is collapsed.
Click to expand it.
-
Please register or sign in to post a comment