feat: resource update server notify and client handler #264
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
|
Hi @tzolov, we encountered the following No handler registered issue when try to handle the "notifications/resources/updated" notification on MCP client of our project. I google a lot and found this feature is not implemented, so I submit this PR to add this feature. Could you please help review this PR and add this feature in the following SDK release?
|
Zizo-Vi
changed the title
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.
add resource update handler support to McpAsyncClient，and also add notifyResourcesUpdated to MCP server.
resolve #251
Motivation and Context
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context