Claude-in-Chrome MCP fails to connect on Windows 11 — named pipe not created

Description

Claude-in-Chrome browser automation tools fail to connect on Windows 11. Every mcp__claude-in-chrome__* tool returns "Browser extension is not connected" despite all components being correctly configured.

Environment

• OS: Windows 11 Pro 10.0.26200
• Claude Code: v2.1.97
• Chrome: Running with Claude extension enabled
• Account: Same account logged in on both claude.ai (Chrome) and Claude Code CLI

What works

• Native messaging host registry key exists:

HKCU\Software\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_code_browser_extension

• Manifest points to correct batch file: C:\Users\Admin\.claude\chrome\chrome-native-host.bat
• Batch file invokes claude.exe --chrome-native-host correctly
• Manual native host test works: Running claude --chrome-native-host successfully creates the named pipe \.\pipe\claude-mcp-browser-bridge-Admin and outputs "Initializing..."
• Chrome extension is installed, enabled, toggled off/on, service worker restarted

What fails

• The named pipe \.\pipe\claude-mcp-browser-bridge-Admin is never created automatically — verified with ls //./pipe/claude-mcp-browser-bridge-Admin returning "not found"
• mcp__claude-in-chrome__tabs_context_mcp always returns "Browser extension is not connected"
• mcp__claude-in-chrome__switch_browser also fails with same error
• /chrome command opens Firefox (default browser) instead of Chrome — unrelated but noted

Steps to reproduce

1. Install Claude Code v2.1.97 on Windows 11
2. Install Claude-in-Chrome extension in Google Chrome
3. Log into claude.ai with same account in Chrome
4. Open Chrome with extension enabled
5. In Claude Code CLI, call any mcp__claude-in-chrome__* tool
6. Result: "Browser extension is not connected"

Troubleshooting attempted

• Restarted Chrome completely (closed all windows, reopened)
• Restarted Claude Code (exited, reopened new session)
• Toggled extension off/on in chrome://extensions
• Verified single Chrome profile active
• Confirmed native host works when invoked manually
• Checked no stale Claude processes running

Expected behavior

The MCP server in Claude Code should trigger Chrome to launch the native messaging host, establishing the named pipe connection automatically.

Suspected root cause

The MCP client within Claude Code is not initiating the connection to Chrome's native messaging system. The native host only runs when manually invoked — Chrome's extension never receives the signal to launch it via the native messaging API.