{"version":"2.1.287","anchor":"mcp-passthrough-cleanup-now-skips-dropped-clients","canonical_anchor":"mcp-passthrough-cleanup-now-skips-dropped-clients","heading":"Dropped MCP connections are cleaned up at a different point","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/mcp-passthrough-cleanup-now-skips-dropped-clients","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Dropped MCP connections are cleaned up at a different point\n\nClaude Code no longer cleans up dropped MCP connections at the end of device bridge discovery, and handles them when connections finish instead\n\n**Unclear.** The practical effect for users is not known.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools, and Claude Code keeps a connection, called a client, to each one. When Claude Code finishes discovering MCP servers through its device bridge, it now cleans up only connections that are not marked as dropped. Dropped connections are now cleaned up when the connection step itself finishes.\n\nBefore this change, the end of discovery cleaned up all connections.\n\n**Why**\n\nThis changes how a connection that drops out during discovery is closed down.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}