{"version":"2.1.282","anchor":"claude-in-chrome-can-run-alongside-managed-mcpjson-when-dev","canonical_anchor":"claude-in-chrome-can-run-alongside-managed-mcpjson-when-dev","heading":"Claude in Chrome can be allowed alongside managed-mcp.json, with policy-specific refusals","tier":"use","area":"Chrome & Browser","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/claude-in-chrome-can-run-alongside-managed-mcpjson-when-dev","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Claude in Chrome can be allowed alongside managed-mcp.json, with policy-specific refusals\n\nNew allowClaudeInChromeWithManagedMcp policy lets admins permit Claude in Chrome under managed-mcp.json, and blocked setups now explain why\n\n**Unclear.** When the separate Chrome-specific message for the `--chrome` flag is shown is not clear.\n\n**What**\n\nClaude in Chrome is the browser integration, delivered as a built-in MCP server (MCP is a standard for connecting outside tools). Organizations that deploy a managed MCP configuration, `managed-mcp.json`, take exclusive control of which MCP servers run, and that used to block Claude in Chrome with no way to allow it.\n\n- A new device policy key, `allowClaudeInChromeWithManagedMcp`, is off by default. When it is true and the enterprise configuration was read without fatal errors, Claude in Chrome can run alongside `managed-mcp.json`. `deniedMcpServers` and the organization's Claude in Chrome setting can still block it.\n\n- Without the key, trying to configure Chrome is refused with a Chrome-specific message: \"Claude in Chrome is blocked by your organization's managed MCP configuration (managed-mcp.json). An administrator can allow it with allowClaudeInChromeWithManagedMcp in device policy.\" Before, it got the generic \"You cannot dynamically configure MCP servers when an enterprise MCP config is present\" message.\n\n- The prompt offering to install or set up Claude in Chrome is now also skipped when `managed-mcp.json` blocks Chrome. Before, only `deniedMcpServers` was checked.\n\n- Starting Remote Control with `--chrome` under a blocking policy now prints the specific reason Chrome is blocked, followed by \"Start Remote Control without --chrome.\" It used to print one fixed message naming both an enterprise MCP config and a `deniedMcpServers` entry.\n\n**Why**\n\nAdministrators using `managed-mcp.json` can now opt in to Claude in Chrome. Where it stays blocked, people are no longer offered a setup that cannot work, and error messages name the policy responsible.\n\n- Area: Chrome & Browser\n- Names: `managed-mcp.json`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}