Fixed a bug where the list of enabled MCP servers ignored the caller's actual allowlist and managed-server settings
The internal function that figures out which MCP servers (Model Context Protocol servers, which let Claude Code connect to external tools and data sources) are enabled had a bug: it read the allowedMcpServers and managedMcpServers settings from the wrong variable instead of the one it was actually passed, so it likely used stale or undefined config instead of the real settings. This is now fixed. Additionally, managedMcpServers can now be specified as an object, not just an array.
This bug meant the set of MCP servers Claude Code considered enabled could be wrong regardless of what was actually configured. Fixing it makes allowedMcpServers and managedMcpServers behave as configured, and the added object format for managedMcpServers gives admins more flexibility in how they list managed servers.
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.
* Servers you [provide through `managedMcpServers`](#provide-servers-through-managed-settings)managed-mcp see the edit
Anthropic's documentation has since written up managedMcpServers, on Control MCP server access for your organization.