Ext Ops Panel
Open dashboard
Comparison

Omi vs WhatsApp Chat Reader (Unofficial)

Omi is an MCP server published by BasedHardware. Marketplaces we read that list it: 1 (Docker MCP Catalog). WhatsApp Chat Reader (Unofficial) is an MCP server published by NabheetCloud. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
MarketplaceOmiWhatsApp Chat Reader (Unofficial)
Docker MCP Catalog Listed
Version: sha256:674097f43757
Forks (GitHub): 2 608
Pulls (Docker Hub): 33 761
Stars (Docker Hub): 1
Stars (GitHub): 13 727
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Downloads/month (PyPI): 81
Downloads/week (PyPI): 26
Forks (GitHub): 0
Stars (GitHub): 1
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

Omi vs WhatsApp Chat Reader (Unofficial)
FactOmiWhatsApp Chat Reader (Unofficial)
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)13 727 (better)1 (worse)
Pulls (Docker Hub) (differs)33 761No figure on Docker Hub
Forks (GitHub) (differs)2 608 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/omi)On your machine (wa-chat-reader)
Transportstdiostdio
Tools it declares (differs)6Not published
Environment variables it asks for (differs)1, secrets among them: 15, secrets among them: 0
Parts of the bundle (differs)Not a bundle1
LicenceMITMIT
Repository (differs)github.com/basedhardware/omigithub.com/nabheetcloud/wa-chat-reader
Changes in the last 7 days (differs)02
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

Omi

In its own words, on Docker MCP Catalog:

A Model Context Protocol server for Omi interaction and automation. This server provides tools to read, search, and manipulate Memories and Conversations.

WhatsApp Chat Reader (Unofficial)

In its own words, on Official MCP Registry:

Unofficial read-only MCP server for your local WhatsApp chat history (stays on your machine).

How to run each

Omi As a local MCP server: Docker image

Claude Code
claude mcp add --env "OMI_API_KEY=<YOUR_OMI_API_KEY>" --transport stdio omi -- docker run -i --rm -e OMI_API_KEY mcp/omi

Requires: OMI_API_KEY (secret)

WhatsApp Chat Reader (Unofficial) As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio wa-chat-reader -- uvx wa-chat-reader

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 Chat Reader (Unofficial) publish no list of tools, so we do not compare tools.

Settings each asks for

Only Omi asks for

  • OMI_API_KEY (secret)

Only WhatsApp Chat Reader (Unofficial) asks for

  • WHATSAPP_BACKUP_PATHS
  • WHATSAPP_DB_PATHS
  • WHATSAPP_DEBUG
  • WHATSAPP_LOG_FILE
  • WHATSAPP_MAX_DAYS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Omi · What it can do: WhatsApp Chat Reader (Unofficial) · 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. 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