Claude Code CLI connecting to Chrome MCP returns "not connected" despite extension showing as connected

Resolved 💬 5 comments Opened Apr 9, 2026 by Reshape4890 Closed May 5, 2026

Environment:

  • macOS 14 (Sonoma/Sequoia)
  • Claude Code CLI (latest)
  • Chrome with Claude extension installed
  • Single claude.ai account (xxxx@email.com — same account in extension and Claude Code

Steps to reproduce:

  1. Install Claude browser extension
  2. Set extension to "On All Sites" via Chrome extension permissions
  3. Launch claude from terminal in a project directory
  4. Confirm /mcp panel shows claude-in-chrome · ✓ connected
  5. Confirm /chrome dialog shows Status: Enabled, Extension: Installed, Enabled by default: Yes
  6. Call any mcp__claude-in-chrome__* tool (e.g., tabs_context_mcp)

Expected: Tool returns tab context / connects successfully

Actual: Tool returns:
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.

Notes:

  • Only one Claude account in use — no account mismatch possible
  • Chrome restarted after extension install
  • Claude Code restarted
  • /mcp panel contradicts the tool error by showing the extension as connected
  • "Reconnect extension" option in /chrome dialog does not resolve it
  • Extension site access set to "On All Sites"
  • Feedback ID: 6ae87088-477b-4bb5-bbb6-ed3847d7079e

View original on GitHub ↗

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