{"version":"2.1.221","anchor":"mcp-task-polling-uses-plain-protocol-requests-instead-of-the","canonical_anchor":"mcp-task-polling-uses-plain-protocol-requests-instead-of-the","heading":"MCP task polling uses plain protocol requests instead of the experimental tasks client","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-task-polling-uses-plain-protocol-requests-instead-of-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### MCP task polling uses plain protocol requests instead of the experimental tasks client\n\nMCP task polling now uses plain protocol calls instead of an experimental client path.\n\n**What**\n\ngetTask, getTaskResult and cancelTask no longer go through the SDK's experimental tasks namespace.\n\n**Details**\n\n- replaced by direct requests for \"tasks\/get\", \"tasks\/result\" and \"tasks\/cancel\"\n- each request carries an explicit result schema\n\n**Evidence**\n\n`{ method: \"tasks\/cancel\", params: { taskId: i } }`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}