The claude-in-chrome MCP server now wires its browser MCP server config into the session's existing MCP connections owner, logging a warning (no MCP connections owner on this session; the browser tools land on the next reconcile) if none exists yet and deferring adoption until the next reconcile. A related helper now detects MCP server configs referencing the --claude-in-chrome-mcp flag (via command or args), likely to identify the Chrome MCP connector during config processing.
claude-in-chrome MCP server now adopts into existing connection owner
The Chrome MCP server now properly attaches to the session's existing MCP connection owner.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Chrome & BrowserArea: what it touches
Bug FixesKind: in v2.1.260,
Bug FixesSection of the release