Managed settings can now supply MCP servers directly ("managed" as a first-class MCP source)

Managed settings can now supply MCP servers directly via a new managedMcpServers key, read from policy settings and merged in alongside enterprise, local, project, and user MCP servers. This key only allows http/sse servers with https:// URLs (no stdio/command, no ${VAR} expansion) and is validated with checks for control/invisible characters; if it appears in any settings source other than managed settings, it is rejected and a warning is shown. Servers delivered this way cannot be removed locally, and their URLs/headers are masked in the UI as "(value set by your organization)".

A new "managed" scope joins enterprise/user/project/local throughout the settings and MCP system, with its own settings file, a "Managed settings (provided by your organization)" label, and an "MCP servers" label of "Managed MCPs." A helper (WJ) now treats "managed" the same as "enterprise" for the managed-policy gate governing MCP approval and server lookup. When running under Claude Desktop's third-party entrypoint or as a local agent, this new source is skipped entirely, and a warning explains that Claude Desktop supplies and locks the session's MCP servers itself. Managed gateway settings validation also now points admins at managedMcpServers instead of the previous "not supported yet" message when it sees mcpServers under managed settings.