Ext Ops Panel
Open dashboard
Comparison

nodriver — Chrome browser automation vs io.github.cherchyk/browser

nodriver — Chrome browser automation is an MCP server published by andresolbach. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). io.github.cherchyk/browser is an MCP server published by cherchyk. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-25. 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

Where each is published
Marketplacenodriver — Chrome browser automationio.github.cherchyk/browser
Official MCP Registry Listed
Version: 2.6.1
Downloads/month (PyPI): 534
Downloads/week (PyPI): 328
Forks (GitHub): 0
Stars (GitHub): 6
Not marked · First seen
Listed
Version: 0.2.1
Downloads/month (npm): 1 542
Downloads/week (npm): 583
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen
PyPI (MCP servers) Listed
Version: 2.6.1
Downloads/month (PyPI): 534
Downloads/week (PyPI): 328
Forks (GitHub): 0
Stars (GitHub): 6
Not marked · First seen
Not listed
npm registry (MCP servers) Not listed Listed
Version: 0.4.8
Downloads/month (npm): 1 542
Downloads/week (npm): 583
Forks (GitHub): 1
Stars (GitHub): 9
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

nodriver — Chrome browser automation vs io.github.cherchyk/browser
Factnodriver — Chrome browser automationio.github.cherchyk/browser
Marketplaces that list it22
Stars (GitHub) (differs)6 (worse)9 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)2026-10-16Not published
Where it runs (differs)On your machine (nodriver-mcp)On your machine (mcpbrowser)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 0Not published
Licence (differs)Not statedMIT
Repository (differs)github.com/andresolbach/nodriver-mcp-servergithub.com/cherchyk/mcpbrowser
Changes in the last 7 days00
First seen2026-10-112026-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

nodriver — Chrome browser automation

In its own words, on Official MCP Registry:

Chrome automation via nodriver: 70 tools, isolated browsers, profiles and configurable startup.

io.github.cherchyk/browser

In its own words, on Official MCP Registry:

MCP server for loading authenticated web pages using Chrome DevTools Protocol

How to run each

nodriver — Chrome browser automation As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio nodriver-mcp-server -- uvx nodriver-mcp

io.github.cherchyk/browser As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio browser -- npx -y mcpbrowser

Commands 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 io.github.cherchyk/browser publish no settings it asks for, so we do not compare settings.

What it can do: nodriver — Chrome browser automation · What it can do: io.github.cherchyk/browser · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built