browser-harness vs io.github.dynamicupgrade/chromedebug
browser-harness is a plugin bundle for AI coding tools published by browser-use. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.dynamicupgrade/chromedebug is an MCP server published by dynamicupgrade. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |  browser-harness | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.1.0 Forks (GitHub): 1 808 Stars (GitHub): 18 417 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.9.6 Downloads/month (npm): 2 585 Downloads/week (npm): 730 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 | browser-harness | io.github.dynamicupgrade/chromedebug |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 18 417 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 808 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@dynamicu/chromedebug-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/browser-use/browser-harness | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
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
browser-harness
Open-source browser agent driven via CDP — direct browser control, 79K stars, YC W25. browser-harness gives Claude Code direct, low-level control of a real Chrome browser via the Chrome DevTools Protocol. Coordinate-level clicks pass through iframes, shadow DOM, and cross-origin frames at the compositor level — no selector hunting, no Playwright wrappers. Connects to a long-running Browser Use Cloud or local browser session, so logins persist across runs. Highlights: - Screenshot-first workflow: capture → read pixel → click_at_xy → re-capture to verify - Bulk HTTP fetch helper for static pages (no browser overhead) - Raw CDP escape hatch for anything helpers don’t cover - Interaction skills for dialogs, dropdowns, iframes, shadow DOM, file uploads, cross-origin frames - Remote browsers via Browser Use Cloud — share a live URL with a human when login/CAPTCHA blocks the agent
io.github.dynamicupgrade/chromedebug
Record browser bugs - frames, clicks and console logs - and hand them to your AI over MCP.
How to run each
browser-harness As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install browser-harness@claude-communityio.github.dynamicupgrade/chromedebug As a local MCP server: npm package
claude mcp add --transport stdio chromedebug -- npx -y @dynamicu/chromedebug-mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: browser-harness · What it can do: io.github.dynamicupgrade/chromedebug · 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.