com.clauxel.chromedevtoolsmcp/chromedevtoolsmcp-mcp vs io.github.codeChap/agent-browser
com.clauxel.chromedevtoolsmcp/chromedevtoolsmcp-mcp is an MCP server published by chromedevtoolsmcp.clauxel.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.codeChap/agent-browser is an MCP server published by codeChap. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |  com.clauxel.chromedevtoolsmcp/chromedevtoolsmcp-mcp |  io.github.codeChap/agent-browser |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 1 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 | com.clauxel.chromedevtoolsmcp/chromedevtoolsmcp-mcp | io.github.codeChap/agent-browser |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (chromedevtoolsmcp.clauxel.com/mcp) | Not stated |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/clauxel/chrome-devtools-session-mcp-mcp | github.com/codechap/mcp-server-agent-browser |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | No HTTP response at the last check (8 h ago) | no remote endpoint we check |
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
com.clauxel.chromedevtoolsmcp/chromedevtoolsmcp-mcp
A paid remote MCP for AI agent browser DevTools MCP, built to return verdicts, receipts, usage logs,
io.github.codeChap/agent-browser
MCP server for browser automation via Vercel's agent-browser CLI
How to run each
com.clauxel.chromedevtoolsmcp/chromedevtoolsmcp-mcp As a remote MCP server
claude mcp add --transport http chromedevtoolsmcp-mcp https://chromedevtoolsmcp.clauxel.com/mcpio.github.codeChap/agent-browser
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.clauxel.chromedevtoolsmcp/chromedevtoolsmcp-mcp has a remote endpoint we check. How we check endpoints
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: com.clauxel.chromedevtoolsmcp/chromedevtoolsmcp-mcp · What it can do: io.github.codeChap/agent-browser · Compare two other plugins
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.