[DOCS] Managed MCP docs omit `allowAllClaudeAiMcps` behavior for Claude.ai connectors

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/managed-mcp

Section/Topic

Exclusive control with managed-mcp.json and the managed MCP settings reference for enterprise connector policy

Current Documentation

The managed MCP page currently says:

If you deploy a managed-mcp.json file, Claude Code loads only the servers that file defines. Users cannot add, modify, or use any other MCP servers, including plugin-provided servers and claude.ai connectors.

The same page currently describes the supported patterns as:

Fixed deployment | Every user gets the same servers and can't add others | managed-mcp.json with the servers you want Approved catalog | Publish a list of approved servers; users add the ones they want, anything else is blocked | allowedMcpServers + allowManagedMcpServersOnly: true

The settings reference currently documents these managed MCP keys:

allowedMcpServers | When set in managed-settings.json, allowlist of MCP servers users can configure. Undefined = no restrictions, empty array = lockdown. Applies to all scopes. Denylist takes precedence. allowManagedMcpServersOnly | (Managed settings only) Only allowedMcpServers from managed settings are respected. deniedMcpServers still merges from all sources. Users can still add MCP servers, but only the admin-defined allowlist applies. deniedMcpServers | When set in managed-settings.json, denylist of MCP servers that are explicitly blocked. Applies to all scopes including managed servers. Denylist takes precedence over allowlist.

There is no documented entry for allowAllClaudeAiMcps.

What's Wrong or Missing?

Changelog v2.1.149 says:

Enterprise: added the allowAllClaudeAiMcps managed setting to load claude.ai cloud MCP connectors alongside managed-mcp.json

A. The exclusive-control wording is now outdated

The managed MCP page still says that deploying managed-mcp.json prevents any claude.ai connectors from loading. After v2.1.149, enterprise admins can explicitly allow Claude.ai cloud MCP connectors alongside managed-mcp.json, so the current wording overstates how absolute that restriction is.

B. The new managed setting is undocumented

The docs do not explain that allowAllClaudeAiMcps exists, where admins should configure it, or how it changes the behavior of managed-mcp.json deployments.

C. The interaction with existing MCP policy controls is unclear

The current docs only describe managed-mcp.json, allowedMcpServers, allowManagedMcpServersOnly, and deniedMcpServers. They do not explain how allowAllClaudeAiMcps interacts with those controls or what users should expect to see in /mcp when the setting is enabled.

Suggested Improvement

Update the managed MCP docs to describe allowAllClaudeAiMcps as an enterprise managed setting that allows Claude.ai cloud MCP connectors to load alongside a deployed managed-mcp.json.

At minimum:

1. Revise the managed-mcp.json exclusivity text so it reflects the new exception when allowAllClaudeAiMcps is enabled.
2. Add an allowAllClaudeAiMcps entry to the settings reference with its scope and behavior.
3. Document how this setting interacts with allowedMcpServers, allowManagedMcpServersOnly, and deniedMcpServers.
4. Clarify the user-visible result in /mcp when enterprise-managed servers and Claude.ai connectors are both available.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/managed-mcp | 25-34 | Pattern table lists only managed-mcp.json, allowlists, and denylists; no allowAllClaudeAiMcps option |
| https://code.claude.com/docs/en/managed-mcp | 43-52 | Says managed-mcp.json prevents any claude.ai connectors from loading |
| https://code.claude.com/docs/en/settings | 175-177, 198 | Managed MCP settings list omits allowAllClaudeAiMcps |
| https://code.claude.com/docs/en/server-managed-settings | 126 | Current limitation text mentions delivering only allowedMcpServers and deniedMcpServers for this policy area |
| https://code.claude.com/docs/en/mcp | 750-776 | User-facing Claude.ai connector docs do not mention enterprise behavior when managed-mcp.json is also deployed |

Total scope: 4 pages affected

Version context: behavior changed in v2.1.149