Ext Ops Panel
Open dashboard
Comparison

Hyperbrowser vs grab-cookie

Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). grab-cookie is a plugin bundle for AI coding tools published by Mike Bramm. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
MarketplaceHyperbrowsergrab-cookie
Docker MCP Catalog Listed
Version: sha256:11ed80138c33
Forks (GitHub): 75
Pulls (Docker Hub): 41 195
Stars (Docker Hub): 3
Stars (GitHub): 789
Not marked · First seen
Not listed
Community marketplace servosity/msp-skills Not listed Listed
Version: 0.1.0
Forks (GitHub): 13
Stars (GitHub): 59
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 grab-cookie
FactHyperbrowsergrab-cookie
Marketplaces that list it11
Stars (GitHub) (differs)789 (better)59 (worse)
Pulls (Docker Hub) (differs)41 195No figure on Docker Hub
Forks (GitHub) (differs)75 (better)13 (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
Licence (differs)MITApache-2.0
Repository (differs)github.com/hyperbrowserai/mcpgithub.com/servosity/msp-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14

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.

grab-cookie

In its own words, on Community GitHub marketplaces:

Capture, store, wire, and verify a browser-session credential for sites that issue no API key and no OAuth: httpOnly session cookies, opaque localStorage bearer tokens, and custom auth headers. One DevTools Copy as cURL paste is the only human step; extraction, storage in the Windows Credential Manager or macOS Keychain, config regeneration, live verification, and expiry warning are automated. Complements connect-tool, which deliberately refuses cookie import. Markdown plus stdlib Python, no compiled binary and no MCP server.

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)

grab-cookie As a Claude Code plugin

Claude Code
/plugin marketplace add servosity/msp-skills
/plugin install grab-cookie@msp-skills

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

Tools each declares

The marketplaces of grab-cookie publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Hyperbrowser · What it can do: grab-cookie · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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