{"version":"2.1.323","anchor":"mcp-projectlocal-scope-tracks-declaring-directory-managed","canonical_anchor":"mcp-projectlocal-scope-tracks-declaring-directory-managed","heading":"Admins can allow Claude in Chrome alongside managed MCP servers","tier":"use","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-projectlocal-scope-tracks-declaring-directory-managed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Admins can allow Claude in Chrome alongside managed MCP servers\n\nA new managed setting, `allowClaudeInChromeWithManagedMcp`, lets Claude in Chrome run when an organisation deploys managed MCP servers\n\n**What**\n\nMCP servers are add-ons that give Claude Code extra tools. Organisations can deploy a fixed set of them through `managed-mcp.json`. A new managed setting, `allowClaudeInChromeWithManagedMcp`, lets the built-in Claude in Chrome server run alongside that managed set. Managed settings are the ones an administrator sets for everyone in an organisation.\n\nClaude Code also now records which folder each project or local MCP configuration was read from, and it can tell when a project server was declared somewhere else.\n\n**Why**\n\nEnterprise admins get a new control: they can keep a managed MCP setup and still allow Claude in Chrome.\n\n- Area: Managed Settings\n- Names: `allowClaudeInChromeWithManagedMcp`, `managed-mcp.json`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}