René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Support progress flow","articleBody":"**Expected Behavior**\n\n- There is a [Progress Flow](https://modelcontextprotocol.io/specification/2025-03-26/basic/utilities/progress#progress-flow) spec on MCP.\n- When the client sends the `params._meta.progressToken`, the server may send progress notifications.\n\n**Current Behavior**\n\n- The SDK doesn't supports it currently\n\n**Context**\n\n\u003c!--- \nHow has this issue affected you?\nWhat are you trying to accomplish?\nWhat other alternatives have you considered?\nAre you aware of any workarounds?\n--\u003e\n\n- Some clients times out when there is no progress event from server.\n- Of course the specification says \"MAY\", but it is also true that server doesn't supports the spec.\n- Also, when the tool task is long task, the UX can lead to bad, that can't tell if it's stuck or not.\n\nRelated tasks:\n\n- [x] Fix the Tool Call handling to allow processing additional metadata parameters from the full CallToolRequest object, enabling features like progress tracking. #351 -\u003e replaced by #375\n- [x] Extend the McpSchema to include the `_meta` and `_meta.progressToken` parameters to all Request types. #352\n- [ ] ~~Implement McpServer to McpClient progress notification, extending the exchange implementations. The #300 is partially related.~~\n- [ ] ~~Implement the McpClient to McpServer progress notifications. #389~~\n- [x] Implement McpServer and McpClient progress notification. #407 \n","author":{"url":"https://github.com/134130","@type":"Person","name":"134130"},"datePublished":"2025-06-08T06:56:38.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/298/java-sdk/issues/298"}