{"version":"2.1.259","anchor":"cached-remote-managed-mcp-servers-withheld-until-session-con","canonical_anchor":"cached-remote-managed-mcp-servers-withheld-until-session-con","heading":"Cached remote managed MCP servers withheld until session confirms them","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/cached-remote-managed-mcp-servers-withheld-until-session-con","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Cached remote managed MCP servers withheld until session confirms them\n\nCached org-managed MCP servers are withheld until the server reconfirms them this session, with a warning explaining the wait.\n\nIf `managedMcpServers` exist in a cached remote settings payload but haven't been reconfirmed by the current session's live payload, they are withheld from taking effect rather than applied immediately. A status-only warning is shown explaining that the organization's MCP servers are withheld until the server confirms them this session, and they connect automatically as soon as it does.\n\n- Area: MCP\n- Names: `managedMcpServers`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}