claude-code - 💡(How to fix) Fix Chrome MCP returns `permission_required` with no UI to approve domain

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The mcp__Claude_in_Chrome__* tools (used to drive the Claude in Chrome extension from Claude Code) return permission_required: <domain> errors when first targeting a new domain. There is no visible UI surface in the extension to approve that domain — the "Your approved sites" list in the extension popup never gets populated through any flow I can find, so the permission never clears and the tool calls remain blocked indefinitely.

The Claude in Chrome side panel can still act on the same site (it surfaces per-task approval inline), so the underlying connection between extension and account works. The bug appears to be specifically in the cross-app approval flow between Claude Code (CLI) and the Chrome extension.

Error Message

Either (a) a prompt surfaces in the extension when Claude Code tries a new domain, allowing approval; (b) the extension's "Your approved sites" list has an "Add site" affordance; or (c) the error message in Claude Code includes a direct path to grant the permission.

Root Cause

The mcp__Claude_in_Chrome__* tools (used to drive the Claude in Chrome extension from Claude Code) return permission_required: <domain> errors when first targeting a new domain. There is no visible UI surface in the extension to approve that domain — the "Your approved sites" list in the extension popup never gets populated through any flow I can find, so the permission never clears and the tool calls remain blocked indefinitely.

The Claude in Chrome side panel can still act on the same site (it surfaces per-task approval inline), so the underlying connection between extension and account works. The bug appears to be specifically in the cross-app approval flow between Claude Code (CLI) and the Chrome extension.

Fix Action

Fix / Workaround

The tool stays permanently blocked for that domain. Reinstalling the extension does not clear it. The only workaround is to abandon the Claude Code → Chrome MCP path entirely and paste prompts directly into the Claude in Chrome side panel, which uses per-task approval that does work.

RAW_BUFFERClick to expand / collapse

Summary

The mcp__Claude_in_Chrome__* tools (used to drive the Claude in Chrome extension from Claude Code) return permission_required: <domain> errors when first targeting a new domain. There is no visible UI surface in the extension to approve that domain — the "Your approved sites" list in the extension popup never gets populated through any flow I can find, so the permission never clears and the tool calls remain blocked indefinitely.

The Claude in Chrome side panel can still act on the same site (it surfaces per-task approval inline), so the underlying connection between extension and account works. The bug appears to be specifically in the cross-app approval flow between Claude Code (CLI) and the Chrome extension.

Reproduction

  1. Have Claude in Chrome extension installed and connected.
  2. In Claude Code, attempt to drive a site via any mcp__Claude_in_Chrome__* tool (e.g., mcp__Claude_in_Chrome__navigate to https://adsmanager.facebook.com/...).
  3. The tool returns permission_required: adsmanager.facebook.com (or similar for the target domain).
  4. Open the Claude in Chrome extension popup → "Your approved sites" list is empty.
  5. No prompt or UI surface appears in the extension or in Claude Code to approve the domain.

Expected

Either (a) a prompt surfaces in the extension when Claude Code tries a new domain, allowing approval; (b) the extension's "Your approved sites" list has an "Add site" affordance; or (c) the error message in Claude Code includes a direct path to grant the permission.

Actual

The tool stays permanently blocked for that domain. Reinstalling the extension does not clear it. The only workaround is to abandon the Claude Code → Chrome MCP path entirely and paste prompts directly into the Claude in Chrome side panel, which uses per-task approval that does work.

Environment

  • macOS Darwin 23.6.0
  • Claude Code with Opus 4.7 model
  • Claude in Chrome extension — fresh reinstall on 2026-05-16 (bug reproduced after reinstall)
  • The same cross-app flow worked on 2026-04-04 via the Cowork desktop app, which uses a different connection path — so the regression appears specific to the Claude Code CLI ↔ Chrome extension link.

Impact

Blocks any Claude Code automation of web apps that don't have a dedicated MCP (e.g., Facebook Ads Manager, other non-integrated SaaS tools). Forces a manual paste-and-screenshot workflow as the only fallback.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Chrome MCP returns `permission_required` with no UI to approve domain