Improvements / v2.1.310
Clarify MCP elicitation timeout error
CHANGELOG · original
Changed the error for an MCP tool call that times out in a non-interactive session while the server's elicitation is unanswered: it now tells Claude that no answer came and not to repeat the call Open official changelog ↗ Documentation
Documentation excerpt
MCP tool call timed out with the server's question unanswered
In non-interactive mode, an MCP server asked for input through elicitation during a tool call, and the call's time limit ran out before an answer came:
MCP server "<name>" tool "<tool>" timed out after <N>s. The server asked the user a question, and no answer came before the time limit. Do not call this tool again in this turn. Tell the user that the server's question got no answer, and wait for their reply.
Before v2.1.310, the result ended at timed out after <N>s and said nothing about the question.
What to do:
- Set up an
Elicitationhook that answers the server's requests - In a TypeScript Agent SDK application, make your
onElicitationcallback return its answer before the limit runs out - To give an answer more time, set a longer
timeoutin milliseconds in the server's configuration entry, such as"timeout": 600000for 10 minutes - Run the task in an interactive session instead and answer the server's dialog yourself
Documentation snapshot · 2026-11-20