Fix MCP protocol compliance: use 'notifications/initialized' method #10
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
The MCP specification defines the initialized notification method as 'notifications/initialized', not just 'initialized'. This change fixes the protocol compliance issue where clients sending the correct 'notifications/initialized' notification would get 'No handler for notification' errors. Changes: - Updated server.go to register handler for 'notifications/initialized' - Updated corresponding test to check for the correct method name Fixes protocol compliance with MCP specification as defined in: https://github.com/modelcontextprotocol/typescript-sdk/blob/main/src/types.ts
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.
Problem
The MCP server framework was registering a notification handler for
"initialized"instead of the correct"notifications/initialized"method as defined in the MCP specification. This caused protocol compliance issues where clients sending the proper"notifications/initialized"notification would receive "No handler for notification" errors.Solution
Updated the framework to use the correct method name
"notifications/initialized"as specified in the MCP protocol.Changes
"initialized"to"notifications/initialized"References
Testing
This fix resolves the "No handler for notification: notifications/initialized" error that users were experiencing when using MCP clients that correctly implement the protocol.