{"version":"2.1.221","anchor":"mcp-request-handlers-moved-to-string-method-names-and-the-ne","canonical_anchor":"mcp-request-handlers-moved-to-string-method-names-and-the-ne","heading":"MCP request handlers moved to string method names and the new request object","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-request-handlers-moved-to-string-method-names-and-the-ne","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### MCP request handlers moved to string method names and the new request object\n\nMCP request handling was updated to a newer library shape, including prompts and task status updates.\n\n**What**\n\nInternal MCP call sites were updated to the newer SDK shape.\n\n**Details**\n\n- Handlers register by literal method name and read the abort signal off the request wrapper rather than a separate extra argument.\n- Elicitation registers on \"elicitation\/create\" and uses the request's own signal.\n- Task status notifications register on \"notifications\/tasks\/status\" with an explicit params schema and read taskId and status off the notification directly.\n\n**Evidence**\n\n`notifications\/tasks\/status`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}