{"version":"2.1.221","anchor":"connected-client-record-exposes-protocol-details-and-goes-th","canonical_anchor":"connected-client-record-exposes-protocol-details-and-goes-th","heading":"Connected client record exposes protocol details and goes through an adoption hook","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/connected-client-record-exposes-protocol-details-and-goes-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Connected client record exposes protocol details and goes through an adoption hook\n\nConnected MCP servers now track their negotiated protocol, and a failed wiring step no longer breaks the connection.\n\n**What**\n\nThe object returned for a connected MCP server carries protocol metadata and is handed to a registered wiring callback.\n\n**Details**\n\n- The record now includes `negotiatedProtocolVersion` and `protocolEra` alongside capabilities and instructions.\n- After building it, the connect path calls a registered wiring callback.\n- If that callback throws, the connection still succeeds and a warning is logged saying the placeholder is retained 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"}