[Feature Request] "Control Chrome" MCP integration — add Windows support (currently macOS only)

Resolved 💬 2 comments Opened Mar 1, 2026 by argravatar2012 Closed Mar 5, 2026

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?

The "Control Chrome" MCP integration (developed by Anthropic) currently only supports macOS. It uses Chrome's AppleScript API, which is macOS-exclusive.

Windows users cannot install or use this integration. The Requirements section in Claude Desktop's MCP marketplace shows a warning icon next to "macOS" with the note: "This extension may not work correctly until all requirements are met."

This means Windows users are completely locked out of the ability to control Chrome through Claude Desktop — including critical tools like execute_javascript, get_page_content, open_url, and tab management.

Given that a significant portion of Claude Desktop users are on Windows, this is a major gap in functionality.

What Should Happen?

The "Control Chrome" MCP integration should support Windows in addition to macOS.

On Windows, Chrome can be controlled programmatically via:

  1. Chrome DevTools Protocol (CDP) — cross-platform, no OS-specific API needed
  2. Puppeteer / Playwright — Node.js-based, works on all platforms
  3. Native Messaging API — Chrome's built-in extension communication

Since the MCP already requires Node.js >=16.0.0, a CDP or Puppeteer-based approach would make Windows support straightforward without breaking existing macOS functionality.

Error Messages/Logs

N/A — The integration simply cannot be installed on Windows. The MCP marketplace shows a warning: "This extension may not work correctly until all requirements are met" with macOS listed as unmet requirement.

Steps to Reproduce

  1. Open Claude Desktop on Windows
  2. Go to the MCP integrations marketplace
  3. Find "Control Chrome" (developed by Anthropic)
  4. See the Requirements section — macOS is listed with a warning icon
  5. Attempting to install shows: "This extension may not work correctly until all requirements are met"

Claude Model

N/A

Is this a regression?

No, this never worked — Windows support was never available

Last Working Version

N/A

Claude Code Version

Claude Desktop (latest) on Windows 11

Platform

Anthropic API

Operating System

Windows 11

Terminal/Shell

N/A — this is about Claude Desktop MCP marketplace, not CLI

Additional Information

This is a feature request, not a bug report. Filing here as there is no separate feature request template.

The "Control Chrome" MCP is developed by Anthropic and is listed in Claude Desktop's built-in MCP marketplace. It currently relies on Chrome's AppleScript API, which is macOS-exclusive.

Why this matters:
Windows has the largest desktop OS market share. Excluding Windows users from browser control capabilities significantly limits the usefulness of Claude Desktop's MCP ecosystem on the most popular platform.

Suggested implementation:
Replace or supplement the AppleScript-based approach with Chrome DevTools Protocol (CDP), which works identically on all platforms. This would enable Windows (and Linux) support with minimal architectural changes.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗