Claude in Chrome extension not connecting despite MCP server showing connected
Resolved 💬 6 comments Opened Jan 29, 2026 by chuck-markin-IS Closed May 5, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Environment:
- OS: Windows
- Claude Code version: 2.1.23
- Chrome extension: Claude in Chrome (beta)
- Chrome version: [please add your Chrome version - find it at chrome://settings/help]
Description:
The Claude in Chrome browser extension fails to connect from Claude Code, even though the MCP server shows as connected.
Steps to reproduce:
- Install Claude in Chrome (beta) extension
- Enable extension with "On all sites" permission
- Run Claude Code CLI
- Run /mcp - shows claude-in-chrome server is connected
- Attempt to use any browser automation tool (e.g., tabs_context_mcp)
- Receive error: "Browser extension is not connected"
Troubleshooting attempted:
- Uninstalled and reinstalled the Chrome extension
- Restarted Chrome completely
- Verified extension permissions ("On all sites" enabled)
- Reconnected MCP server via /mcp
- Checked extension DevTools console - no errors
- Extension sidebar opens normally
Expected behavior:
Browser automation tools should connect to the Chrome extension when MCP server shows connected.
Actual behavior:
All browser automation tool calls return "Browser extension is not connected" error.
Chrome Version: 144.0.7559.97
What Should Happen?
Claude should connect to my browser. Everything was working fine until yesterday.
Error Messages/Logs
Steps to Reproduce
- Install Claude in Chrome (beta) extension from Chrome Web Store
- Enable extension with "On all sites" site access permission 3. Open Claude Code CLI in terminal
- Run /mcp - confirm claude-in-chrome server shows as connected
- Attempt any browser automation (e.g., ask Claude to browse to a URL)
- Tool call to tabs_context_mcp returns error: "Browser extension is not connected"
Additional info:
- Reinstalling extension does not fix
- Restarting Chrome does not fix
- Reconnecting MCP via /mcp does not fix
- No errors visible in extension's DevTools console
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.23
Claude Code Version
2.1.23
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗