[BUG] Claude in Chrome: script.google.com blocked after update (v1.0.68) — was working yesterday

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?

After updating Claude in Chrome to v1.0.68, script.google.com (Google Apps Script editor) is completely blocked. All MCP tool calls (screenshot, read_page, get_page_text, javascript_tool) return "Permission denied for this action on this domain". This was working fine yesterday. Reinstalling the extension does not fix it, confirming this is a server-side domain block. Other domains like base.next-engine.org and developer.next-engine.com are also blocked.

What Should Happen?

MCP tools should work on script.google.com as they did before the update. Chrome extension "Site access" is already set to "All sites".

Error Messages/Logs

Permission denied for this action on this domain

Steps to Reproduce

1. Open Google Apps Script editor (script.google.com) in a Chrome tab
2. Add the tab to Claude's MCP tab group
3. Attempt any MCP action (screenshot, read_page, get_page_text, javascript_tool)
4. All return: "Permission denied for this action on this domain"
5. Chrome extension "Site access" is set to "All sites"
6. Reinstalling the extension does not fix the issue

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

1.0.67

Claude Code Version

2.1.107

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

This breaks GAS (Google Apps Script) development workflows where Claude reads/writes code via MCP. Having to use Gyazo screenshots as a workaround is extremely inefficient.

Blocked domains observed:

• script.google.com
• base.next-engine.org
• developer.next-engine.com

Troubleshooting already attempted:

• Set "Site access" to "All sites"
• Enabled "Allow access to file URLs"
• Uninstalled and reinstalled the extension
• None of the above fixed the issue