{"version":"2.1.260","anchor":"claude-in-chrome-mcp-server-now-adopts-into-existing-connect","canonical_anchor":"claude-in-chrome-mcp-server-now-adopts-into-existing-connect","heading":"claude-in-chrome MCP server now adopts into existing connection owner","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-now-adopts-into-existing-connect","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### claude-in-chrome MCP server now adopts into existing connection owner\n\nThe Chrome MCP server now properly attaches to the session's existing MCP connection owner.\n\nThe 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.\n\n- Area: Chrome & Browser\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}