Under the hood
Useful2 Signal0
MCP task polling now uses plain protocol calls instead of an experimental client path.
What's wrong with this entry?
Anonymous. No account, no email.
What
getTask, getTaskResult and cancelTask no longer go through the SDK's experimental tasks namespace.
Details
- replaced by direct requests for "tasks/get", "tasks/result" and "tasks/cancel"
- each request carries an explicit result schema
Evidence
{ method: "tasks/cancel", params: { taskId: i } }
Strings lifted out of the shipped bundle, so the claim above can be checked against them.