managedMcpServers

A Claude Code settings key, read out of the shipped bundle. It was in the build from v2.1.259 and was gone by v2.1.284.

Releases whose published page names managedMcpServers.

1. v2.1.305 20 Oct 2026
   A setting named attributionProjectPolicy appears next to other managed settings

   The name attributionProjectPolicy now appears in a list of settings alongside managedMcpServers

   found in this entry's text

2. v2.1.300 14 Oct 2026
   Admins can block plugin MCP servers by address, and Claude Code reads more managed settings

   A new managed setting, deniedPluginMcpServers, blocks plugin MCP servers by address, and six more managed settings now list Claude Code as a reader

   found in this entry's text

3. v2.1.299 14 Oct 2026
   Clearer messages when an MCP server uses a name or address Claude Code reserves

   MCP servers configured with a reserved name or address are now refused with an explicit message saying why

   found in this entry's text

4. v2.1.299 14 Oct 2026
   Plugins can read the managed MCP server list, and call timeouts are clearer

   Plugins reading policy settings now see managed MCP servers, and calls that time out get their own error

   found in this entry's text

5. v2.1.293 7 Oct 2026
   Desktop admin policy gains marketplace and MCP tool-policy options

   Admin policy for the desktop app gains a live-apply rule for plugin marketplaces and a per-server tool policy override in managedMcpServers

   found in this entry's text

6. v2.1.293 7 Oct 2026
   Hosted managed MCP config now refuses client secrets except Google ones

   Hosted managed config now rejects an MCP server's OAuth client secret unless it is a Google client, and points others to oauth.clientSecretHelper

   found in this entry's text, named in this entry

7. v2.1.283 25 Sep 2026
   CLAUDE_CODE_GB_BASE_URL gets the same settings checks as the proxy variables

   CLAUDE_CODE_GB_BASE_URL joins the proxy, certificate and bridge variables that Claude Code checks when it cleans a settings file

   found in this entry's text

8. v2.1.273 15 Sep 2026
   New managed-only settings key: isolation

   The new 'isolation' settings key is now managed-only, like managedMcpServers, and gets stripped with a warning if set elsewhere

   found in this entry's text

9. v2.1.269 11 Sep 2026
   Fixed a bug in MCP server enumeration that ignored the caller's arguments

   Fixed a bug where the list of enabled MCP servers ignored the caller's actual allowlist and managed-server settings

   found in this entry's text, named in this entry

10. v2.1.267 9 Sep 2026
    New "sec-default" hooks module locks plugins out of classic hooks/prompt/settings/tool policy for managed orgs

    A new sec-default hooks module blocks plugins from bypassing policy settings and MCP server allowlists on managed and Team/Enterprise accounts

    found in this entry's text

11. v2.1.260 3 Sep 2026
    Managed MCP server config gets a formal deprecation/migration system

    Legacy managed MCP server config fields now have a formal deprecation and rewrite system.

    found in this entry's text

12. v2.1.260 3 Sep 2026
    New credential-header safety warning for MCP config and inference headers

    MCP and inference config now warn when headers look like they leak credentials over plain HTTP or shared tokens.

    found in this entry's text

13. v2.1.260 3 Sep 2026
    MCP toolPolicy simplified: ask-session mode dropped from the wildcard rule docs

    MCP toolPolicy docs and wildcard logic were simplified by dropping the ask-session case.

    found in this entry's text

14. v2.1.259 2 Sep 2026
    Cached remote managed MCP servers withheld until session confirms them

    Cached org-managed MCP servers are withheld until the server reconfirms them this session, with a warning explaining the wait.

    found in this entry's text, named in this entry

15. v2.1.259 2 Sep 2026
    Managed settings can now supply MCP servers directly ("managed" as a first-class MCP source)

    Organizations can push HTTPS MCP servers straight from managed settings; they can't be removed locally and their URLs are masked.

    found in this entry's text, named in this entry

16. v2.1.259 2 Sep 2026
    managedMcpServers added to managed-settings merge semantics

    Managed-settings merge semantics now cover org-supplied MCP servers, with the higher-priority source winning name collisions.

    found in this entry's text, named in this entry

17. v2.1.259 2 Sep 2026
    New validator function warns on managedMcpServers entries

    A validator now warns about org-supplied MCP server entries that are ignored.

    found in this entry's text, named in this entry

18. v2.1.259 2 Sep 2026
    MCP cold-start now waits for a second, unverified-cache confirmation stage

    MCP cold start now waits for remote managed-settings confirmation when org MCP servers are withheld from the cache.

    found in this entry's text, named in this entry

The earliest release whose published evidence quoted managedMcpServers was v2.1.259, 2 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

5 further spans in the ledger name it. The list above is the earliest first and stops at 6.

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.