claude-in-chrome: extension shows as not connected despite valid install, login, and "Reconnect extension"

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 7, 2026

tabs_context_mcp (and other mcp__claude-in-chrome__* tools) consistently return:

Browser extension is not connected. Please ensure the Claude browser extension is installed and running (https://claude.ai/chrome), and that you are logged into claude.ai with the same account as Claude Code. If this is your first time connecting to Chrome, you may need to restart Chrome for the installation to take effect.

Troubleshooting already performed (all confirmed, issue persists):

  • Extension is installed and enabled in chrome://extensions, no errors shown
  • Logged into claude.ai with the same account used in Claude Code
  • Chrome fully restarted (all windows closed, not just the tab)
  • New Claude Code session started
  • Used the "Reconnect extension" option — does not resolve the issue
  • Repeated tabs_context_mcp calls across multiple attempts, same failure every time

Key detail that rules out extension/account misconfiguration:
From another interface, using the same claude.ai account, the browser correctly shows as connected. This suggests the problem is isolated to this specific Claude Code environment/session rather than the extension installation or account credentials.

Expected behavior:
tabs_context_mcp should successfully connect to the browser extension given a valid install, matching account, and confirmed working connection from another interface with the same account.
Actual behavior:
Connection fails every time with the "Browser extension is not connected" error, unaffected by "Reconnect extension" or a full Chrome/session restart.

View original on GitHub ↗