{"version":"2.1.269","anchor":"fixed-a-bug-in-mcp-server-enumeration-that-ignored-the-calle","canonical_anchor":"fixed-a-bug-in-mcp-server-enumeration-that-ignored-the-calle","heading":"Fixed a bug in MCP server enumeration that ignored the caller's arguments","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/fixed-a-bug-in-mcp-server-enumeration-that-ignored-the-calle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Fixed a bug in MCP server enumeration that ignored the caller's arguments\n\nFixed a bug where the list of enabled MCP servers ignored the caller's actual allowlist and managed-server settings\n\n**What**\n\nThe 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.\n\n**Why**\n\nThis 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.\n\n- Area: MCP\n- Names: `managedMcpServers`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}