Legacy managed MCP server config fields now have a formal deprecation and rewrite system.
A new deprecation system now governs legacy forms in managedMcpServers[] entries. Old-style fields like an oauth.scopes list, a toolPolicy of "ask-session", transport:"builtin", and authorityHost are each mapped to a rewrite rule with a defined support window; once support ends, an entry still in the old form is rejected outright and that connector becomes unavailable until rewritten. authorityHost support has already ended: it is now rejected with the message authorityHost was removed: set azureCloud ("us-gov-high" for GCC High) instead.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
| <span id="managedmcpservers" />Managed MCP servers<br />`managedMcpServers` | `object[]` | MDM + Bootstrap<br />Added in 1.2581.0 | — | Org-pushed MCP servers: remote (HTTP/SSE) or local (stdio command). May embed bearer tokens. Deprecat…third-party/claude-desktop/configuration see the edit
| <span id="managedmcpservers" />Managed MCP servers<br />`managedMcpServers` | `object[]` | MDM + Bootstrap<br />Added in 1.2581.0 | — | Org-pushed MCP servers: remote (HTTP/SSE) or local (stdio command). May embed bearer tokens. Deprecat…third-party/claude-desktop/configuration see the edit
Anthropic's documentation has since written up authorityHost, on Configuration reference.
Changed Claude apps gateway to also refuse to start, naming the field, when a desktop policy misspells a field in a nested object of a…