modelcontextprotocol / modelcontextprotocol/servers
Add cancellation handling to Everything server
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe.
For testing with the Inspector, add handling of CancelledNotificationSchema messages to stop the long-running process example.
Describe the solution you'd like
- The UI (in a related PR to the Inspector repo) would track the id of the long-running process, and expose a button that lets you cancel.
- The
everythingserver in this repo would handle the message and cancel the long-running process.
Describe alternatives you've considered
Not doing it.
Additional context
This idea was raised in this PR to the inspector repo.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Everything server and its long-running process example, then read the CancelledNotificationSchema handling discussed in the linked Inspector PR. Done means the server receives cancellation for the tracked process and stops it; verify this through the repository's existing server tests or example workflow if available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100