{"version":"2.1.247","anchor":"mcp-servers-can-ask-for-input-from-inside-a-task","canonical_anchor":"mcp-servers-can-ask-for-input-from-inside-a-task","heading":"MCP servers can ask for input from inside a task","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/mcp-servers-can-ask-for-input-from-inside-a-task","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### MCP servers can ask for input from inside a task\n\nMCP servers can now ask you for input from inside a running task.\n\n**What**\n\nMCP prompts for user input (`elicitation\/create`) are now resolved per request rather than through a shared handler, and MCP tasks get their own resolver that also serves `roots\/list`.\n\n**Details**\n\n- The resolver receives the server name, request parameters, request id and a cancellation signal.\n- Any other method is declined with a message naming the request and the unsupported method.\n- In a non-interactive session with no UI to prompt in, the request is logged and dropped instead of hanging.\n\n**Evidence**\n\n`input request '${e}' has unsupported method ${t.method}`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}