allowClaudeInChromeWithManagedMcp
A Claude Code settings key, read out of the shipped bundle. It has been in the build since v2.1.282, including the newest one read.
A new device policy setting, allowClaudeInChromeWithManagedMcp, lets Claude in Chrome run even when managed-mcp.json controls MCP servers
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.282.
In the changelogs
2Releases whose published page names allowClaudeInChromeWithManagedMcp.
-
v2.1.282
Admins can allow Claude in Chrome alongside a managed MCP configuration
A new device policy setting,
allowClaudeInChromeWithManagedMcp, lets Claude in Chrome run even whenmanaged-mcp.jsoncontrols MCP serversfound in this entry's text
-
v2.1.282
Claude in Chrome setup is no longer offered when a managed MCP config blocks it
Claude Code now skips the Claude in Chrome install offer when your organization's managed MCP config would block the Chrome connection
found in this entry's text
First cited
1The earliest release whose published evidence quoted allowClaudeInChromeWithManagedMcp was v2.1.282, 24 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
2One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.