Hyperbrowser vs sessions-dashboard
Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). sessions-dashboard is a plugin bundle for AI coding tools published by channyzf6. 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
| Marketplace |  Hyperbrowser |  sessions-dashboard |
|---|---|---|
| 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: 0.5.1 Forks (GitHub): 0 Stars (GitHub): 0 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 | Hyperbrowser | sessions-dashboard |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 789 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 41 173 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 75 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/hyperbrowser) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 1, secrets among them: 0 |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/hyperbrowserai/mcp | github.com/channyzf6/sessions-dashboard |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 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
Hyperbrowser
A MCP server implementation for hyperbrowser.
sessions-dashboard
Live browser dashboard of every CLI agent session you're running on one screen. See what each session is doing in real time, organize them into named groups that persist across restarts, and jump straight to a session's terminal in one click (macOS / Windows + WezTerm).
How to run each
Hyperbrowser As a local MCP server: Docker image
claude mcp add --env "HYPERBROWSER_API_KEY=<YOUR_HYPERBROWSER_API_KEY>" --transport stdio hyperbrowser -- docker run -i --rm -e HYPERBROWSER_API_KEY mcp/hyperbrowserRequires: HYPERBROWSER_API_KEY (secret)
sessions-dashboard As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install sessions-dashboard@claude-communityCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of sessions-dashboard publish no list of tools, so we do not compare tools.
Settings each asks for
Only Hyperbrowser asks for
HYPERBROWSER_API_KEY (secret)
Only sessions-dashboard asks for
SESSIONS_DASHBOARD_HOST
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Hyperbrowser · What it can do: sessions-dashboard · 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.