[BUG] laude in Chrome MCP blocks all domain navigation.

Open 💬 0 comments Opened Jul 13, 2026 by elizabethlemoine33-commits

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?

When using the Claude in Chrome MCP tool in Claude Code, all domain navigation is blocked with "Navigation to this domain is not allowed" — even google.com. This happens despite the Chrome extension having an empty domain allowlist (no restrictions configured).

What Should Happen?

Claude should be able to navigate to any domain not explicitly blocked, consistent with the empty allowlist configured in the extension settings.

Error Messages/Logs

Navigation to this domain is not allowed

Steps to Reproduce

Install the Claude in Chrome Chrome extension
Connect it to Claude Code (desktop app)
Open a session and invoke any tool that calls mcp__claude-in-chrome__navigate with any URL (e.g. https://www.google.com)
Error returns immediately: "Navigation to this domain is not allowed"
Confirm the Chrome extension's domain allowlist is empty — no domains are blocked on the user side

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.200 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

The computer-use MCP can see the browser in read-only mode via screenshot, confirming the extension is connected and functional. The block appears to be enforced server-side within the MCP tool itself, not by the extension configuration.

View original on GitHub ↗