[BUG] Chrome extension MCP shows connected but "Browser extension is not connected" error

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

The Chrome extension MCP server shows as "connected" in Claude
Code (via /mcp command), but all mcp__claude-in-chrome__* tool
calls return "Browser extension is not connected" error.

## Environment

• Claude Code version: 2.1.25
• OS: Windows
• Chrome extension: Installed and enabled, shows no errors in

popup

## What was tried

• Restarting Chrome
• Restarting Claude Code
• Running /chrome command multiple times
• Verifying extension is enabled
• Checking extension popup (shows no errors)

Chrome extension works in chrome, it's just not connecting via /chrome.
I've reconnected, and it opens a new tab in chrome but does not connect still.

What Should Happen?

## Expected behavior
Tools should connect when MCP shows connected and extension is
enabled.

Error Messages/Logs

none.

Steps to Reproduce

1. Install Claude-in-Chrome extension
2. Open Chrome
3. Start Claude Code
4. Run /mcp - shows chrome extension as connected
5. Try any chrome tool (e.g., tabs_context_mcp)
6. Get error: "Browser extension is not connected"

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.25

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Cursor

Additional Information

_No response_