devharness vs Chrome Debugger MCP
devharness is an MCP server published by InDate. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Chrome Debugger MCP is an MCP server published by BitePro. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |  devharness |  Chrome Debugger MCP |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.17.17 Downloads/month (npm): 2 360 Downloads/week (npm): 1 088 Forks (GitHub): 5 Stars (GitHub): 19 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.4 Downloads/month (npm): 149 Downloads/week (npm): 43 Forks (GitHub): 0 Stars (GitHub): 1 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 | devharness | Chrome Debugger MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 19 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 5 (better) | 0 (worse) |
| Last release (differs) | 2026-11-01 | Not published |
| Where it runs (differs) | On your machine (devharness) | On your machine (chrome-debugger-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/indate/devharness | github.com/bitepro/chrome-debugger-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
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
devharness
MCP server that connects AI assistants to Chrome DevTools Protocol for runtime debugging - set breakpoints, inspect variables, monitor network traffic, and automate browser interactions
Chrome Debugger MCP
Chrome breakpoint debugging MCP server for inspecting runtime values and stepping through code
How to run each
devharness
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Chrome Debugger MCP As a local MCP server: npm package
claude mcp add --transport stdio chrome-debugger-mcp -- npx -y chrome-debugger-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: devharness · What it can do: Chrome Debugger MCP · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. 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.