{"version":"2.1.296","anchor":"mcp-stdio-servers-on-windows-are-closed-via-stdin-first-wit","canonical_anchor":"mcp-stdio-servers-on-windows-are-closed-via-stdin-first-wit","heading":"Windows MCP servers get a chance to shut down cleanly","tier":"notice","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/mcp-stdio-servers-on-windows-are-closed-via-stdin-first-wit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Windows MCP servers get a chance to shut down cleanly\n\nOn Windows, Claude Code now closes an MCP server's input and waits before force-closing it, instead of killing it at once\n\n**What**\n\nMCP (Model Context Protocol) servers are add-ons that give Claude extra tools. A stdio server is one that runs as a separate program on your computer and talks to Claude Code through its standard input and output.\n\nOn Windows, when Claude Code shuts such a server down, it now closes the server's input first and waits. It only force-closes the server and any programs it started if the server is still running after that wait. This also applies to servers that never finished connecting. Before, Claude Code force-closed them straight away.\n\nOn macOS and Linux nothing changes: Claude Code still sends its usual series of stop signals.\n\n**Why**\n\nWindows MCP servers can now finish what they are doing and exit on their own, rather than being cut off mid-task.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}