Bug Report: Chrome Extension Not Connecting in Claude Code (Terminal) but Works in Claude Desktop

Bug Report: Chrome Extension Not Connecting in Claude Code (Terminal) but Works in Claude Desktop
Environment

• Claude Code Version: 2.1.25
• OS: Windows 11 Home Single Language (NT 10.0.26200.0)
• Node.js Version: v24.13.0

Description

The claude-in-chrome MCP server fails to connect to the Chrome browser extension when using Claude Code (terminal/CLI), but works
correctly with Claude Desktop on the same machine.

Steps to Reproduce

1. Install Claude browser extension from https://claude.ai/chrome
2. Open Claude Desktop → Chrome extension connects successfully ✓
3. Open terminal and run claude
4. Use any mcp__claude-in-chrome__* tool (e.g., tabs_context_mcp)
5. Receive error: "Browser extension is not connected"

Expected Behavior

The Chrome extension should connect to Claude Code (terminal) the same way it connects to Claude Desktop.

Actual Behavior

• Claude Desktop: Extension connects and works
• Claude Code (terminal): Always returns "Browser extension is not connected"

Troubleshooting Attempted

• Restarted Chrome completely
• Verified extension is enabled in chrome://extensions
• Confirmed Chrome process is running
• Ran claude mcp list (shows no custom MCP servers - using built-in)

Additional Context

The MCP tools are available in Claude Code (can call them), but the browser extension never establishes a connection. This suggests the
MCP server is running but cannot communicate with the extension.