Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] claude-in-chrome MCP: tabs_context_mcp always returns "Browser extension is not connected" despite extension showing connected [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48410•Fetched 2026-04-16 07:00:56
View on GitHub
Comments
1
Participants
2
Timeline
9
Reactions
0
Author
mysterFengmysterFeng
Participants
github-actions[bot]github-actions[bot]mysterFengmysterFeng
Timeline (top)
labeled ×5cross-referenced ×2commented ×1unlabeled ×1

Error Message

Error Messages/Logs

Code Example

~/Library/Logs/Claude*/chrome-native-host.log shows socket created and listening, but no client ever connects:                                                                                                                    
  Socket created successfully at: /tmp/claude-mcp-browser-bridge-builder/26774.sock                                                                                                                                                 
  Entering main message loop                                                       
  Socket server listening for connections
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

MCP server shows connected in /mcp panel, Chrome extension UI also shows connected, but every call to tabs_context_mcp returns "Browser extension is not connected".

What Should Happen?

Environment:

  • macOS Darwin 23.3.0
  • Claude Code CLI (latest)
  • Chrome extension installed and enabled

Error Messages/Logs

~/Library/Logs/Claude*/chrome-native-host.log shows socket created and listening, but no client ever connects:                                                                                                                    
  Socket created successfully at: /tmp/claude-mcp-browser-bridge-builder/26774.sock                                                                                                                                                 
  Entering main message loop                                                       
  Socket server listening for connections

Steps to Reproduce

  1. Open Chrome, confirm extension shows connected
  2. In Claude Code, /mcp shows claude-in-chrome · connected
  3. Call tabs_context_mcp → always fails
  4. Restarting Chrome, Claude Code, and reconnecting via /mcp all have no effect

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.109 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue may be resolved by investigating the socket connection between the Chrome extension and the Claude Code MCP server, as the logs indicate that the socket is created and listening but no client connects.

Guidance

  • Verify that the socket file /tmp/claude-mcp-browser-bridge-builder/26774.sock exists and has the correct permissions.
  • Check the Chrome extension's configuration to ensure it is attempting to connect to the correct socket path.
  • Investigate potential issues with the socket connection, such as firewall rules or other system configurations that may be blocking the connection.
  • Consider debugging the Chrome extension to see if it is sending any error messages or logs that may indicate why it is not connecting to the socket.

Example

No code snippet is provided as the issue does not contain sufficient information to create a relevant example.

Notes

The issue may be related to a regression in the Claude Code version 2.1.109, as it worked in a previous version. However, without more information about the previous working version, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Investigate and resolve the socket connection issue, as it is likely the root cause of the problem. This may involve modifying the Chrome extension or the Claude Code MCP server configuration to ensure a stable connection.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#SSR setup#ISR setup#authentication setup#request error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] claude-in-chrome MCP: tabs_context_mcp always returns "Browser extension is not connected" despite extension showing connected [1 comments, 2 participants]