Hyperbrowser vs WhatsApp Web MCP Server
Hyperbrowser is an MCP server published by hyperbrowserai. Marketplaces we read that list it: 1 (Docker MCP Catalog). WhatsApp Web MCP Server is an MCP server published by mario-andreschak. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:11ed80138c33 Forks (GitHub): 75 Pulls (Docker Hub): 41 384 Stars (Docker Hub): 3 Stars (GitHub): 789 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 Downloads/month (npm): 253 Downloads/week (npm): 62 Forks (GitHub): 10 Stars (GitHub): 29 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 | WhatsApp Web MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 789 (better) | 29 (worse) |
| Pulls (Docker Hub) (differs) | 41 384 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 75 (better) | 10 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/hyperbrowser) | On your machine (mcp-whatsapp-web) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 16, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hyperbrowserai/mcp | github.com/mario-andreschak/mcp-whatsapp-web |
| 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.
WhatsApp Web MCP Server
WhatsApp MCP via web.js or browserless Baileys: messages, media, chats, groups and contacts
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/hyperbrowser
Requires: HYPERBROWSER_API_KEY (secret)
WhatsApp Web MCP Server As a local MCP server: npm package
claude mcp add --transport stdio mcp-whatsapp-web -- npx -y mcp-whatsapp-web
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of WhatsApp Web MCP Server publish no list of tools, so we do not compare tools.
Settings each asks for
Only Hyperbrowser asks for
HYPERBROWSER_API_KEY (secret)
Only WhatsApp Web MCP Server asks for
BAILEYS_SESSION_DIRBROWSER_EXECUTABLE_PATHFFMPEG_PATHHEALTH_CHECK_INTERVAL_MSLOG_LEVELLOG_STDERR_LEVELMCP_HTTP_HOSTMCP_HTTP_PORTMCP_OAUTHTOOL_READY_TIMEOUT_MSWA_WEB_VERSIONWHATSAPP_BACKEND
Show the remaining 4
WHATSAPP_HEADLESSWHATSAPP_NO_SANDBOXWHATSAPP_PAIRING_PHONE_NUMBERWHATSAPP_SESSION_DIR
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Hyperbrowser · What it can do: WhatsApp Web MCP Server · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.