{"version":"2.1.283","anchor":"mcp-server-stderr-no-longer-dumped-on-connect-failure-once-s","canonical_anchor":"mcp-server-stderr-no-longer-dumped-on-connect-failure-once-s","heading":"MCP server error output is no longer logged when Claude Code is already shutting down","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/mcp-server-stderr-no-longer-dumped-on-connect-failure-once-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### MCP server error output is no longer logged when Claude Code is already shutting down\n\nIf an MCP server fails to connect after shutdown cleanup has begun, Claude Code no longer logs that server's error output\n\n**Unclear.** It is unclear whether this log line ever reached you on screen or only went to the debug log.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. When one fails to connect, Claude Code logs the error text the server printed. It now does this only if Claude Code has not yet started cleaning up to exit. Before, it always logged it.\n\n**Why**\n\nThis cuts out misleading MCP error lines when you end a session while servers are still connecting.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}