{"version":"2.1.293","anchor":"mcp-never-answered-error-no-longer-says-the-answer-stream","canonical_anchor":"mcp-never-answered-error-no-longer-says-the-answer-stream","heading":"Shorter error when an MCP server never answers a tool call","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/mcp-never-answered-error-no-longer-says-the-answer-stream","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Shorter error when an MCP server never answers a tool call\n\nThe error for an MCP tool call that got no answer now says only that the server never answered, and drops the line about the answer stream ending\n\n**What**\n\nMCP servers are add-on programs that give Claude Code extra tools. When one of them never answers a tool call, meaning a request to use one of its tools, the error now reads `MCP server \"<server>\" never answered tool \"<tool>\".` It still says that the outcome is unknown and that you should check what the call did before running it again.\n\nThe earlier explanation that \"the stream that was to bring its answer ended first\" has been removed.\n\n**Why**\n\nBoth you and Claude read this message after a dropped call, so the guidance each of you gets about what happened is now different.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}