{"version":"2.1.221","anchor":"newly-connected-mcp-clients-are-handed-to-a-wiring-hook-that","canonical_anchor":"newly-connected-mcp-clients-are-handed-to-a-wiring-hook-that","heading":"Newly connected MCP clients are handed to a wiring hook that can fail safely","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/newly-connected-mcp-clients-are-handed-to-a-wiring-hook-that","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Newly connected MCP clients are handed to a wiring hook that can fail safely\n\nNewly connected MCP servers can now replace a cached placeholder, and a failure there won't break the connection.\n\n**What**\n\nBoth MCP connect paths now pass the freshly built connected client to a global `getConnectedClientWiring()` callback, so a cached placeholder can be adopted by the real client.\n\n**Details**\n\n- the server's memo keys are cleared before the callback runs\n- if the callback throws, the connection still succeeds and only a per-server debug line is written, stating the placeholder is kept and adoption will retry\n\n**Evidence**\n\n`connected-client wiring failed (placeholder retained, adoption will retry): `\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}