Claude in Chrome: Browser extension not connected on Windows despite correct setup
Resolved 💬 3 comments Opened Feb 6, 2026 by Hyunchule Closed Feb 6, 2026
Bug Description
tabs_context_mcp always returns "Browser extension is not connected" on Windows, despite all setup steps being completed correctly.
Environment
- OS: Windows 11
- Claude Code version: 2.1.33
- Chrome extension: Claude in Chrome (Beta) v1.0.45
- Claude Desktop: installed
Setup Confirmed
- Chrome extension installed and enabled
- Logged into claude.ai with the same account as Claude Code
/mcpcommand returns "Reconnected to claude-in-chrome" successfullyclaudeInChromeDefaultEnabled: truein settingshasCompletedClaudeInChromeOnboarding: truein settingscachedChromeExtensionInstalled: truein settings
Native Messaging Host
The native messaging host JSON file points to Claude Desktop's executable (chrome-native-host.exe). Registry key exists at HKCU\Software\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_browser_extension.
What Was Tried
- Disabling Native Messaging Host file (renamed to .disabled) + Chrome restart
- Removing registry key + Chrome restart
- Restoring both file and registry key + Chrome restart
- Uninstalling and reinstalling the Chrome extension
- Running with Claude Desktop open (Claude in Chrome enabled/disabled in Desktop)
- Running without Claude Desktop
- Multiple Chrome full restarts
- Refreshing claude.ai tab
- Calling
tabs_context_mcpwithcreateIfEmpty: true
None of the above resolved the issue.
Expected Behavior
tabs_context_mcp should detect and connect to the Chrome extension.
Actual Behavior
Every call returns:
Browser extension is not connected. Please ensure the Claude browser extension is installed and running...
The MCP server reconnects successfully via /mcp, but every tool call returns the above error.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗