{"version":"2.1.261","anchor":"new-mcp-set-servers-binding-changed-sync-hook","canonical_anchor":"new-mcp-set-servers-binding-changed-sync-hook","heading":"New mcp_set_servers binding-changed sync hook","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/new-mcp-set-servers-binding-changed-sync-hook","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### New mcp_set_servers binding-changed sync hook\n\nMCP server config changes now trigger sync hooks to keep SDK hosts' binding state in sync.\n\nThe control-request handler for `mcp_set_servers` now calls a `.sync(\"binding_changed\")` hook before applying server config changes, with a `.sync(\"startup\")` hook invoked earlier during session init. This appears to be new plumbing for keeping an SDK host's server-binding state in sync with dynamic MCP server updates.\n\n- Area: MCP\n- Names: `mcp_set_servers`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}