[BUG] Claude for Chrome MCP tools return "Navigation to this domain is not allowed" for ALL domains (v1.0.66+ regression)

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?

Summary

Claude for Chrome extension (Beta) v1.0.68, when driven via Claude Code
MCP browser tools (mcp__Claude_in_Chrome__navigate, screenshot,
read_page, find, computer), returns permission errors for EVERY
domain including benign ones like example.com and google.com —
not site-specific. The reactive approval prompt never fires, so
"Your approved sites" stays permanently empty and cannot be populated.

What Should Happen?

Expected behavior

When the agent calls an MCP browser tool on a new domain, the Claude
for Chrome extension side panel should show a "Permission required"
prompt with an "Always allow actions on this site" button (per the
documented reactive approval model). After one approval, the domain
joins "Your approved sites" and subsequent calls succeed.

Actual behavior

All MCP browser-tool calls error immediately, with no prompt ever
firing. Errors observed:

• mcp__Claude_in_Chrome__navigate → Navigation to this domain is not allowed
• mcp__Claude_in_Chrome__screenshot → Permission denied for this action on this domain
• mcp__Claude_in_Chrome__read_page → Permission denied for reading pages on this domain
• mcp__Claude_in_Chrome__find → Permission denied for reading pages on this domain

Error Messages/Logs

The errors are IDENTICAL for every domain tested: `example.com`,
`google.com`, `supabase.com`, `vercel.com`, `zenmonkey.app.n8n.cloud`.
This indicates the block is upstream of the extension's site-access
layer (probably in the MCP wrapper).

Steps to Reproduce

Steps to reproduce (100% reliable)

1. Install Claude for Chrome (Beta) v1.0.68.
2. chrome://extensions/ → Claude → Details → Site access: "On all sites". Verified.
3. Open a new Chrome tab.
4. In Claude Code, ask the agent: "navigate to example.com".
5. Agent returns: Navigation to this domain is not allowed. No prompt appears anywhere.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Extension version: v1.0.68 Beta

Claude Code Version

Claude Code: v1.0.68

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Related

• Existing regression thread: #43255 (opened 2026-04-03, still unresolved 16+ days later)
• Multiple community reports at community.anthropic.com under the same error string

Impact

Blocks paid Claude Pro use of Claude for Chrome for 100+ n8n
automation workflows I operate for production clients. Unable to
drive browser-based agent tasks for 16+ consecutive days. Requesting
pro-rata refund via billing@anthropic.com in parallel.

Requested resolution

1. P1 investigation into MCP wrapper — the block fires BEFORE the

extension's permission-prompt code path, so approvals can never happen.

1. Document any interim config flag or admin setting that re-enables

per-domain approval prompts.

1. Publish an ETA for v1.0.69 fix.