Chrome MCP extension not connecting - browser extension not detected

Description

The mcp__claude-in-chrome__tabs_context_mcp tool consistently returns "Browser extension is not connected" despite the Chrome extension being installed and confirmed working by the user.

The Chrome MCP tools appear in the deferred tools list (ToolSearch) but claude mcp list does not show any chrome MCP server configured — suggesting the tool definitions are loaded but no actual MCP server bridge is running to connect to the browser extension.

Steps to Reproduce

1. Start Claude Code CLI session (v2.1.81)
2. Confirm Chrome extension is installed, enabled, and user is logged into claude.ai with the same account
3. Call mcp__claude-in-chrome__tabs_context_mcp (with or without createIfEmpty: true)
4. Tool returns connection error every time

Expected Behavior

Tool should detect the Chrome extension and return tab context, enabling browser automation workflows.

Actual Behavior

Returns: "Browser extension is not connected. Please ensure the Claude browser extension is installed and running..."

All Troubleshooting Attempted

| # | Action | Result |
|---|--------|--------|
| 1 | tabs_context_mcp — no params | ❌ "not connected" |
| 2 | tabs_context_mcp — with createIfEmpty: true | ❌ "not connected" |
| 3 | Repeated calls (6+ attempts across multiple turns) | ❌ Same error every time |
| 4 | Confirmed same account in Chrome + Claude Code | ✅ Verified by user |
| 5 | Confirmed extension is active/working in Chrome | ✅ Verified by user |
| 6 | Ran /chrome local command in Claude Code | No output, no effect |
| 7 | claude mcp list | Chrome MCP not listed — only plugin:episodic-memory (failed) and plugin:context7 (connected) |
| 8 | claude mcp list \| grep chrome | "No chrome MCP found" |
| 9 | New session (separate conversation) | ❌ Same behavior |

Root Cause Hypothesis

The Chrome MCP tool definitions are present in the deferred tools registry (visible via ToolSearch), but no corresponding MCP server is actually configured or running. claude mcp list confirms no chrome-related server exists. This means the tools are callable in name only — there's no bridge process to communicate with the browser extension.

Environment

| Component | Version |
|-----------|---------|
| macOS | 26.1 (Build 25B78) |
| Kernel | Darwin 25.1.0 |
| Claude Code | 2.1.81 |
| Model | claude-opus-4-6 (1M context) |
| Node.js | v22.22.0 |
| npm | 10.9.4 |
| Chrome | Running with extension installed + confirmed working |

Impact

Blocking browser-dependent workflows — specifically reading Canvas LMS quiz content for exam preparation. Workaround: manual copy-paste of question text, which is significantly slower.

🤖 Generated with Claude Code