You'll notice
Useful3 Signal3
MCP servers can now ask you for input from inside a running task.
What's wrong with this entry?
Anonymous. No account, no email.
What
MCP 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.
Details
- The resolver receives the server name, request parameters, request id and a cancellation signal.
- Any other method is declined with a message naming the request and the unsupported method.
- In a non-interactive session with no UI to prompt in, the request is logged and dropped instead of hanging.
Evidence
input request '${e}' has unsupported method ${t.method}
Strings lifted out of the shipped bundle, so the claim above can be checked against them.