Claude in Chrome MCP: extension reports connected but tabs_context_mcp returns 'not connected'

Description

The Claude in Chrome browser extension shows as connected on the user's side (extension icon in Chrome), but the MCP server consistently returns:

Browser extension is not connected. Please ensure the Claude browser extension is installed and running...

All mcp__claude-in-chrome__* tools fail with this same error. The extension was working earlier in the same session (successfully automated browser interactions, took screenshots, executed JavaScript, navigated pages). After some period of inactivity, the connection was lost and cannot be re-established.

Steps to Reproduce

1. Start a Claude Code session with --chrome flag
2. Successfully use browser automation tools (tabs_context_mcp, navigate, screenshot, javascript_tool, etc.)
3. After some period (possibly 30+ minutes), the connection drops
4. tabs_context_mcp returns "Browser extension is not connected"
5. switch_browser returns "No other browsers available"
6. The Chrome extension still shows as connected on the browser side
7. No way to re-establish the connection without restarting the session

Environment

• Claude Code CLI
• Chrome with Claude extension installed
• Linux (Ubuntu)
• The extension was actively used earlier in the same conversation session

Expected Behavior

Either:

• The connection should persist for the duration of the session
• Or there should be a way to reconnect without restarting Chrome/session