Ext Ops Panel
Open dashboard
Comparison

Hyperbrowser vs terminal-chromium

Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). terminal-chromium is a plugin bundle for AI coding tools published by gyoz-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-14. 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
MarketplaceHyperbrowserterminal-chromium
Docker MCP Catalog Listed
Version: sha256:11ed80138c33
Forks (GitHub): 75
Pulls (Docker Hub): 41 173
Stars (Docker Hub): 3
Stars (GitHub): 789
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
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

Hyperbrowser vs terminal-chromium
FactHyperbrowserterminal-chromium
Marketplaces that list it11
Stars (GitHub) (differs)789 (better)3 (worse)
Pulls (Docker Hub) (differs)41 173No figure on Docker Hub
Forks (GitHub) (differs)75 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/hyperbrowser)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)10Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle1
LicenceMITMIT
Repository (differs)github.com/hyperbrowserai/mcpgithub.com/gyoz-ai/terminal-chromium-skill
Changes in the last 7 days00
First seen (differs)2026-10-112026-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

Hyperbrowser

In its own words, on Docker MCP Catalog:

A MCP server implementation for hyperbrowser.

terminal-chromium

In its own words, on Claude Code: claude-plugins-community:

Full Chromium browser in your terminal for Claude Code. Launches carbonyl (a terminal Chromium renderer using unicode half-block characters) in a tmux split pane and controls it via CDP (Chrome DevTools Protocol). Browse, click, type, evaluate JS, take screenshots, get accessibility trees, and extract page content -- all programmatically from within a Claude Code session. Works over SSH, renders at 60 FPS, supports WebGL/WebGPU.

How to run each

Hyperbrowser As a local MCP server: Docker image

Claude Code
claude mcp add --env "HYPERBROWSER_API_KEY=<YOUR_HYPERBROWSER_API_KEY>" --transport stdio hyperbrowser -- docker run -i --rm -e HYPERBROWSER_API_KEY mcp/hyperbrowser

Requires: HYPERBROWSER_API_KEY (secret)

terminal-chromium As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install terminal-chromium@claude-community

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of terminal-chromium publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of terminal-chromium publish no settings it asks for, so we do not compare settings.

What it can do: Hyperbrowser · What it can do: terminal-chromium · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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