Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
MCPArea: what it touches
In DevelopmentKind: in v2.1.239,
What probably matters to youSection of the release
Task-result handling requires a per-request opt-in that no code in this build sets.
What
The MCP client can now accept a task result from a server, but only when the individual request opts in, the server advertised the tasks extension, and the payload validates. Nothing in this build sets that opt-in, so every task result currently ends in an unsupported-result-type rejection.
Details
The opt-in flag is read in exactly two places, the request path and the tool-call path, and set in none.
The flag and the extension name did not exist in 2.1.238 at all.
Evidence
io.modelcontextprotocol/tasks
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
