{"version":"2.1.295","anchor":"chromebrowser-mcp-tool-calls-now-use-invoketoolraw","canonical_anchor":"chromebrowser-mcp-tool-calls-now-use-invoketoolraw","heading":"Browser integration lists connected browsers through a tool call","tier":"internal","area":"Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/chromebrowser-mcp-tool-calls-now-use-invoketoolraw","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Browser integration lists connected browsers through a tool call\n\nClaude Code now asks for the list of connected browsers by calling a tool, instead of reading a resource\n\n**Unclear.** Whether this changes anything you can see when using the browser integration is not known.\n\n**What**\n\nMCP (Model Context Protocol) is the system Claude Code uses to talk to outside tools, including its Chrome browser integration. The low-level helper behind these calls changed from reading a resource to invoking a tool. It can now pass the tool's name along with the call.\n\nThe request for the list of connected browsers now uses this tool call. The helper that lists available MCP tools was also reworked.\n\n**Why**\n\nThis may fix how direct calls to the browser integration are made.\n\n- Area: Chrome\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}