{"version":"2.1.311","anchor":"chrome-mcp-server-started-late-via-a-proxy","canonical_anchor":"chrome-mcp-server-started-late-via-a-proxy","heading":"Claude in Chrome's tool server loads only when first used","tier":"internal","area":"Claude in Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/chrome-mcp-server-started-late-via-a-proxy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Claude in Chrome's tool server loads only when first used\n\nClaude in Chrome's MCP server now answers startup checks itself and loads the full server only when a real call arrives\n\n**What**\n\nClaude in Chrome provides its browser tools through an MCP server (an add-on that gives Claude tools). That server now answers the opening handshake, connection checks and the request for its list of tools by itself. It loads the full server only when a real tool call arrives, and then repeats the handshake with it.\n\n**Why**\n\nClaude Code does less work at startup when the browser tools are not used.\n\n- Area: Claude in Chrome\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}