Claude in Chrome (Beta): mcp__claude-in-chrome__* tools unavailable in VS Code extension — needs official workaround documentation

Environment

• Claude Code: 2.1.96 (VS Code extension)
• Claude for Chrome extension: 1.0.66
• OS: macOS Darwin 25.4.0
• Chrome: latest stable

Problem

When using the VS Code extension (not CLI), claude-in-chrome MCP server never appears in the MCP servers list, and Chrome tools (mcp__claude-in-chrome__navigate, mcp__claude-in-chrome__read_page, etc.) are not available via ToolSearch.

What I've verified:

• Native messaging host is installed and running: /Users/kasiaalena/.claude/chrome/chrome-native-host
• Unix socket is active: /tmp/claude-mcp-browser-bridge-kasiaalena/<PID>.sock
• Chrome extension is enabled and authenticated
• claude --chrome in CLI shows: Status: Enabled, Extension: Installed
• VS Code window was reloaded multiple times
• mcp.json does not support claude-in-chrome as a regular MCP server entry (no schema support for chrome key in settings.json)

Note: I see this was partially discussed in #23939 (closed "not planned"), but there's no official documentation of a workaround for VS Code users.

Expected behavior

Chrome tools should be accessible in the VS Code extension, consistent with CLI behavior.

Actual behavior

Chrome tools work in claude --chrome CLI session only. In VS Code extension, they are completely unavailable.

Workaround I found

Running claude --chrome -p "prompt" via the Bash tool inside a VS Code session works as a proxy — but this is undocumented and creates a new subprocess for each request (no session continuity, ~15–30s latency per call).

Request

1. If VS Code support is not planned — please document the Bash workaround officially in https://code.claude.com/docs/en/chrome
2. If VS Code support is planned — please provide an ETA or reopen #23939