Claude-in-Chrome MCP: extension executes but CLI receives 'not connected' error (Windows)

Bug Description

Claude-in-Chrome MCP extension is installed and enabled, but Claude Code CLI consistently receives "Browser extension is not connected" error, even though the extension actually executes the command on the Chrome side.

Steps to Reproduce

1. Install Claude-in-Chrome extension in Chrome
2. Verify extension status in Claude Code: Status: Enabled, Extension: Installed
3. Run /chrome command — shows extension is configured
4. Call tabs_context_mcp (or any other mcp__claude-in-chrome__* tool)
5. Chrome side shows the tool executed successfully (e.g., "Tabs read" appears in the extension UI)
6. CLI receives error: "Browser extension is not connected"

Expected Behavior

The tool result should be returned to the CLI after successful execution in Chrome.

Actual Behavior

The extension processes the request (visible in Chrome UI as "Tabs read"), but the CLI always receives the generic "Browser extension is not connected" error message instead of the actual result.

Environment

• Claude Code version: 2.1.31
• OS: Windows 10/11
• Chrome: latest stable
• Extension: Claude-in-Chrome (installed via claude.ai/chrome)

Troubleshooting Attempted

• Reinstalled the extension
• Restarted Chrome multiple times
• Restarted Claude Code CLI multiple times
• Verified login on claude.ai
• Confirmed MCP status shows Enabled/Installed

Additional Context

The disconnect appears to be in the response path — the request reaches the extension and is executed, but the response does not make it back to the CLI. This suggests a possible WebSocket or message-passing issue on Windows.