Claude in Chrome MCP reports "connected" but tool calls fail with "Browser extension is not connected"

Resolved 💬 3 comments Opened Feb 4, 2026 by 999Ineff Closed Feb 8, 2026

Environment:

Claude Code v2.1.31
Claude Max subscription (Opus 4.5)
Windows 10/11
Chrome extension v1.0.44
Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn

Description:
The /mcp command shows claude-in-chrome: ✓ connected with 17 tools available. Reconnecting via the menu says
"Reconnected to claude-in-chrome." However, when actually invoking any Chrome tool (e.g., tabs_context_mcp), it fails
with: "Browser extension is not connected."

What's verified working:

Native messaging registry entries exist (HKCU\Software\Google\Chrome\NativeMessagingHosts)
Native host JSON config exists at expected path
Batch file exists and points to correct claude.exe
Chrome extension installed and enabled (no console errors)
Same account logged into claude.ai and Claude Code
Multiple Chrome/Claude Code restarts attempted

Steps to reproduce:

Run /mcp - shows claude-in-chrome connected
Ask Claude to use any Chrome tool
Tool fails with "Browser extension is not connected"Environment:

Claude Code v2.1.31
Claude Max subscription (Opus 4.5)
Windows 10/11
Chrome extension v1.0.44
Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn

What's verified working:

Native messaging registry entries exist (HKCU\Software\Google\Chrome\NativeMessagingHosts)
Native host JSON config exists at expected path
Batch file exists and points to correct claude.exe
Chrome extension installed and enabled (no console errors)
Same account logged into claude.ai and Claude Code
Multiple Chrome/Claude Code restarts attempted

Steps to reproduce:

Run /mcp - shows claude-in-chrome connected
Ask Claude to use any Chrome tool
Tool fails with "Browser extension is not connected"

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗