Skip to content

feat: resource update server notify and client handler #264

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Zizo-Vi
Copy link

@Zizo-Vi Zizo-Vi commented May 26, 2025

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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

@Zizo-Vi
Copy link
Author

Zizo-Vi commented May 27, 2025

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?

image

@Zizo-Vi Zizo-Vi changed the title Client resource update handler feat: resource update server notify and client handler Jun 3, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support notifications/resources/updated
1 participant