{"version":"2.1.317","anchor":"mcp-reconnect-error-text-no-longer-sanitised-through-allowli","canonical_anchor":"mcp-reconnect-error-text-no-longer-sanitised-through-allowli","heading":"Failed MCP reconnect messages now name the server","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/mcp-reconnect-error-text-no-longer-sanitised-through-allowli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Failed MCP reconnect messages now name the server\n\nWhen reconnecting or switching an MCP server on or off fails, the log now names the server, and the error is passed on raw or cleaned up\n\n**Unclear.** When the error is passed on raw and when it is cleaned up is not clear.\n\n**What**\n\nMCP servers are outside services that give Claude Code extra tools. When reconnecting one, or switching one on or off, fails, the log line now includes the server's name.\n\nThe error that comes back is now either the raw message or a cleaned-up version, depending on a new condition. Before, Claude Code decided this by checking a list of approved error messages.\n\n**Why**\n\nThis changes how much error detail is passed back when an MCP server fails to reconnect.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}