{"version":"2.1.260","anchor":"managed-mcp-server-config-gets-a-formal-deprecationmigratio","canonical_anchor":"managed-mcp-server-config-gets-a-formal-deprecationmigratio","heading":"Managed MCP server config gets a formal deprecation\/migration system","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/managed-mcp-server-config-gets-a-formal-deprecationmigratio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Managed MCP server config gets a formal deprecation\/migration system\n\nLegacy managed MCP server config fields now have a formal deprecation and rewrite system.\n\nA 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`.\n\n- Area: MCP\n- Names: `authorityHost`, `azureCloud`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}