{"version":"2.1.265","anchor":"headless-mcp-prewait-can-now-wait-for-specific-remote-mcp-se","canonical_anchor":"mcp-prewait-gains-a-waitremoteservernames-option","heading":"MCP prewait can now target specific remote servers by name","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/headless-mcp-prewait-can-now-wait-for-specific-remote-mcp-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### MCP prewait can now target specific remote servers by name\n\nMCP prewait gains a waitRemoteServerNames option to block on named remote MCP servers, not just local ones\n\n**What**\n\nThe MCP client prewait step, which waits for MCP clients before a turn is dispatched, now accepts a `waitRemoteServerNames` option alongside the existing `localOnly` and `waitForDeferrable` options. In headless mode, this lets the prewait gate also block on specific named non-local MCP servers, not just local-only ones.\n\nNew telemetry fields `remoteByNamePendingBefore`\/`remoteByNamePendingAfter` are reported on the headless MCP prewait telemetry event.\n\n**Why**\n\nThis lets Claude Code wait for particular remote MCP servers it actually depends on for a turn, rather than only being able to wait for local servers or none at all.\n\n- Area: MCP\n- Names: `waitRemoteServerNames`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}