{"version":"2.1.267","anchor":"remote-tools-announce-worker-now-reports-the-dynamic-bridge","canonical_anchor":"remote-tools-announce-worker-now-reports-the-dynamic-bridge","heading":"Remote-tools-announce worker now reports the dynamic bridge MCP server","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/remote-tools-announce-worker-now-reports-the-dynamic-bridge","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Remote-tools-announce worker now reports the dynamic bridge MCP server\n\nRemote tools announcements now report the status of the dynamic bridge MCP server\n\n**What**\n\nThe handler that responds to `remote_tools_announce` requests now includes a `bridgeServer` callback among its dependencies. This callback looks up the app's MCP client that has `scope === \"dynamic\"` and reports its name, configuration, and whether it's disabled.\n\n**Why**\n\nThis lets the remote-tools-announce process include information about the dynamic bridge MCP server, giving a more complete picture of active MCP connections when tools are announced remotely.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}