{"version":"2.1.288","anchor":"another-chrome-mcp-prefix-recognized-mcp-claude-device-ch","canonical_anchor":"another-chrome-mcp-prefix-recognized-mcp-claude-device-ch","heading":"Chrome tools from a claude-device server are recognised as Claude in Chrome tools","tier":"internal","area":"Chrome & Browser","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/another-chrome-mcp-prefix-recognized-mcp-claude-device-ch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Chrome tools from a claude-device server are recognised as Claude in Chrome tools\n\nTools whose names start with mcp__claude-device__chrome_ are now treated as Claude in Chrome tools\n\n**Unclear.** Which Claude Code behaviours depend on this list of Chrome prefixes is not established.\n\n**What**\n\nClaude Code keeps a list of name prefixes that mark a tool as one of the Claude in Chrome browser tools. These tools arrive through MCP (Model Context Protocol), a standard way of plugging outside tools into Claude Code. That list now includes `mcp__claude-device__chrome_`, so Chrome tools served by a server named `claude-device` are recognised along with the others.\n\n**Why**\n\nChrome tools that come from a `claude-device` server are now treated the same way as the Chrome tools Claude Code already knew about.\n\n- Area: Chrome & Browser\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}