claude-mac-chrome vs NexusWindows for Claude
claude-mac-chrome is a plugin bundle for AI coding tools published by yolo-labz. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). NexusWindows for Claude is an MCP server published by pironjulien. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  claude-mac-chrome |  NexusWindows for Claude |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.1.1 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed, marked deprecated Version: 3.0.0 Downloads/month (PyPI): 0 Downloads/week (PyPI): 2 794 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | claude-mac-chrome | NexusWindows for Claude |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (worse) | 4 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-28 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (nexus-windows) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/yolo-labz/claude-mac-chrome | github.com/pironjulien/nexuswindows-claude |
| Changes in the last 7 days (differs) | 0 | 20 or more |
| First seen (differs) | 2026-10-11 | 2026-10-18 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
claude-mac-chrome
Professional Chrome automation for Claude Code on macOS. Deterministic multi-profile detection via Chrome's authoritative Local State catalog combined with email extraction from tab titles and same-email disambiguation via SNSS Sessions/Tabs URL-set overlap. Addresses windows and tabs by stable AppleScript string IDs instead of ordinal indices. Zero user configuration, zero dependencies, shellcheck + shfmt clean.
NexusWindows for Claude
Windows computer use in the background: UI Automation and Win32 messages, every action read back.
How to run each
claude-mac-chrome As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install claude-mac-chrome@claude-communityNexusWindows for Claude As a local MCP server: PyPI package
claude mcp add --transport stdio nexus-windows -- uvx --python 3.14 nexus-windowsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of claude-mac-chrome publish no settings it asks for, so we do not compare settings.
What it can do: claude-mac-chrome · What it can do: NexusWindows for Claude · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.