Repository navigation
'everything' server notification/progress does not seem to work correctly #2621
Description
When using the 'everything' server, testing the longRunningOperation should send progress notifications, I can see them in the EventStream in the Chrome network tab, but he MCP Inspector doesn't react to them, the tool ends with the final response.
I've been trying to implement progress notifications in an MCP server, but I can't get it to work, the intention was to get Claude to react to progress notifications, but I don't even think Claude implements progress notifications because it doesn't send a progressToken. After digging into it and finding the everything server which implements progress, I cannot see what the intention of this functionality is. Having it only available from custom MCP servers to custom MCP clients doesn't seem all that useful, but I also realise all of this is in the very early stages.
To Reproduce
Steps to reproduce the behavior:
- Start everything server
npx @modelcontextprotocol/server-everything streamableHttp - Start MCP Inspector
npx @modelcontextprotocol/inspector - Connect inspector to http://localhost:3001/mcp
- Start the longRunningOperation tool
Expected behavior
I would at least expect the MCP inspector to show that the progress notifications are working. There is a window in the inspector for Server Notifications which doesn't show anything, I would expect them to appear here.
Logs
n/a
Activity
TheGlenn88 commentedon Aug 26, 2025
perhaps this is more of an issue with https://github.com/modelcontextprotocol/inspector - but i'm not sure.
cliffhall commentedon Oct 19, 2026
Closing: superseded by the v2 release.
Thank you for reporting this, and apologies for the long wait for a response.
Since this was filed, the reference servers have been rebuilt for the 2026-07-28 MCP specification (#4857) and released as v2 (2.0.0 on npm for the TypeScript servers, 2026.10.19 on PyPI for the Python servers). Each server now runs on v2 of its SDK, and the behavior described here has either been fixed or no longer exists in the same form. The long-running tool was rewritten for v2 and sends progress notifications whenever the client supplies a progressToken; the report concerned an older release and the Inspector's display.
This is not a judgment on whether the problem was real; it's a consequence of the code it describes having been replaced. This is happening as part of the backlog triage in #4875.
If this still happens on the v2 release, we'd genuinely like to know. Please open a fresh issue with the version you're running and steps to reproduce, and we'll look at it. Note that this repository accepts contributions as issues rather than pull requests; see
CONTRIBUTING.md.Thanks for taking the time to report it.