API: Generalize client notification handlers for SDK client classes

Open
#858 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
api

Research direction

Start by reviewing the McpAsyncClient, McpSyncClient, and StatelessClient classes mentioned in the issue, along with the related request in issue #831. Determine how custom client notification handlers can be supported through composition or inheritance, and consider the requirements of the linked update extension; done means those client classes expose customizable notification handling.

Written by the indexing model from the issue text.

Description

waiting for triage

Issue #831 requests the ability to add custom notifications for the SDK's McpAsync/Sync/StatelssServer classes.

This issue requests the team to enhance the API to allow for custom notification handlers on the McpAsync/Sync/StatelessClient classes. Currently there is no way...through composition or through inheritance...to add custom notification handlers. To create an update extension, both the server notification (sending) and client notification handling must be customizable.

Dominant language
Java
Stars
3.7k
Forks
1.1k
Avg merge
1d 15h
Merged PRs (30d)
9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/java-sdk

All issues in modelcontextprotocol/java-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.