{"version":"2.1.260","anchor":"claude-in-chrome-mcp-server-config-now-recognizes-dcr-oauth","canonical_anchor":"claude-in-chrome-mcp-server-config-now-recognizes-dcr-oauth","heading":"Claude in Chrome MCP server config now recognizes DCR OAuth mode as not-BYO","tier":"internal","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/claude-in-chrome-mcp-server-config-now-recognizes-dcr-oauth","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Claude in Chrome MCP server config now recognizes DCR OAuth mode as not-BYO\n\nChrome MCP config now determines bring-your-own-auth status by checking for non-DCR mode.\n\nThe Claude in Chrome MCP server config now determines bring-your-own-auth-server status by checking `t.oauth.mode !== \"dcr\"` instead of checking for `mode === \"byo\"`. MCP OAuth entries using dynamic client registration (`dcr` mode) are no longer treated as bring-your-own-auth-server for egress-hostname purposes.\n\n- Area: Chrome & Browser\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}