Ext Ops Panel
Open dashboard
Comparison

io.github.dashi96/chromium-bridge vs io.github.ofershap/real-browser

io.github.dashi96/chromium-bridge is an MCP server published by dashi96. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.ofershap/real-browser is an MCP server published by ofershap. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-22. 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
Marketplaceio.github.dashi96/chromium-bridgeio.github.ofershap/real-browser
Official MCP Registry Listed
Version: 0.5.3
Downloads/month (npm): 211
Downloads/week (npm): 31
Forks (GitHub): 0
Stars (GitHub): 10
Not marked · First seen
Listed
Version: 1.2.1
Downloads/month (npm): 688
Downloads/week (npm): 326
Forks (GitHub): 11
Stars (GitHub): 57
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.3.0
Downloads/month (npm): 688
Downloads/week (npm): 326
Forks (GitHub): 11
Stars (GitHub): 57
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

io.github.dashi96/chromium-bridge vs io.github.ofershap/real-browser
Factio.github.dashi96/chromium-bridgeio.github.ofershap/real-browser
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)10 (worse)57 (better)
Forks (GitHub) (differs)0 (worse)11 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (chromium-bridge)On your machine (real-browser-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)github.com/dashi96/chromium-bridgegithub.com/ofershap/real-browser-mcp
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

io.github.dashi96/chromium-bridge

In its own words, on Official MCP Registry:

MCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation

io.github.ofershap/real-browser

In its own words, on Official MCP Registry:

MCP server + Chrome extension for AI browser control with real sessions.

How to run each

io.github.dashi96/chromium-bridge As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio chromium-bridge -- npx -y chromium-bridge

io.github.ofershap/real-browser As a local MCP server: npm package

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

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

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.dashi96/chromium-bridge · What it can do: io.github.ofershap/real-browser · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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