claude-in-chrome: extension shows connected in Chrome but tabs_context_mcp always returns "not connected"

Status Closed — duplicate
Maintainer reply None cached
Activity 1 comment · opened Aug 4, 2026 · closed Aug 15, 2026

The Claude Chrome extension is installed and appears connected/active in Chrome (signed into claude.ai with the same account as Claude Code), but every call from Claude Code to the browser automation tools fails with:

"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..."

Steps taken, none resolved it:

  • Confirmed extension is installed and enabled in chrome://extensions
  • Confirmed signed into claude.ai in Chrome with the same account as Claude Code
  • Fully quit Chrome (Cmd+Q, not just closed the window) and reopened it
  • Retried the connection multiple times after restart — same error every time

Environment:

  • macOS (Darwin)
  • Claude Code CLI, in-session MCP tool: mcp__claude-in-chrome__tabs_context_mcp

Expected: tabs_context_mcp should detect the connected extension and return tab context.
Actual: consistently returns "Browser extension is not connected" regardless of restart.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗