modelcontextprotocol / modelcontextprotocol/servers
'everything' server notification/progress does not seem to work correctly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
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
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
Run the everything server with npx @modelcontextprotocol/server-everything streamableHttp, connect MCP Inspector to http://localhost:3001/mcp, and start longRunningOperation. Compare the progress notifications visible in Chrome's EventStream with the Inspector's Server Notifications view; done means the Inspector displays the progress notifications or the issue is clearly narrowed to the responsible component.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100