tabs_context_mcp returns "Browser extension is not connected" despite correct setup

Resolved 💬 3 comments Opened May 13, 2026 by diogofigueiraa Closed May 17, 2026

Environment

  • OS: Windows 11 Pro 10.0.26200
  • Claude Code: CLI (claude.exe at C:\Users\..\.local\bin\claude.exe)
  • Chrome extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn
  • Extension status: installed, enabled, logged in with same account

## What's configured correctly

  • Native messaging host registered in registry:

HKCU\Software\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_code_browser_extension

  • Manifest JSON exists at:

C:\Users\<user>\AppData\Roaming\Claude Code\ChromeNativeHost\com.anthropic.claude_code_browser_extension.json

  • .bat wrapper exists at: C:\Users\<user>\.claude\chrome\chrome-native-host.bat
  • allowed_origins in manifest matches installed extension ID

## What happens
Every call to mcp__claude-in-chrome__tabs_context_mcp returns:
"Browser extension is not connected. Please ensure the Claude browser extension
is installed and running (https://claude.ai/chrome)..."

## Steps to reproduce

  1. Install Claude Code CLI on Windows
  2. Install Chrome extension (ID: fcoeoabgfenejglbffodgkkbkcdhcgfn)
  3. Log in with same account in both
  4. Run any claude-in-chrome MCP tool → "not connected"

## Expected behavior
Tools connect successfully and return tab context.

View original on GitHub ↗

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