Claude Code / AI Coding Tools

Claude in Chrome MCP tools fail silently — Permission denied on ALL domains

Fix Claude Code Chrome MCP tools failing on all domains when navigating or reading pages Includes evidence for Claude Code troubleshooting demand.

Category
AI Coding Tools
Error signature
"Navigation to this domain is not allowed" / "Permission denied for reading pages on this domain"
Quick fix
Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated

What this error means

"Navigation to this domain is not allowed" / "Permission denied for reading pages on this domain" is a Claude Code failure pattern reported for developers trying to fix claude code chrome mcp tools failing on all domains when navigating or reading pages. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Multiple GitHub issues report Claude in Chrome MCP tools returning “Navigation to this domain is not allowed” and “Permission denied for reading pages on this domain” for ALL domains (docs.google.com, github.com, wikipedia.org, example.com). Issue #49979 and #43255 show tab creation works but navigation/read_page/click tools fail. v1.0.69 also reports permission_required returned for all MCP navigations with approval popup never rendering (#53630). Strong match for Claude Code Chrome MCP authorization flow bug.

Common causes

Quick fixes

  1. Confirm the exact error signature matches "Navigation to this domain is not allowed" / "Permission denied for reading pages on this domain".
  2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
  3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Step-by-step troubleshooting

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. Keep the working fix documented for the team or deployment environment.

How to prevent it

Sources checked

Evidence note: Multiple GitHub issues report Claude in Chrome MCP tools returning “Navigation to this domain is not allowed” and “Permission denied for reading pages on this domain” for ALL domains (docs.google.com, github.com, wikipedia.org, example.com). Issue #49979 and #43255 show tab creation works but navigation/read_page/click tools fail. v1.0.69 also reports permission_required returned for all MCP navigations with approval popup never rendering (#53630). Strong match for Claude Code Chrome MCP authorization flow bug.

FAQ

What should I check first?

Start with the exact "Navigation to this domain is not allowed" / "Permission denied for reading pages on this domain" text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Claude Code workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without "Navigation to this domain is not allowed" / "Permission denied for reading pages on this domain".