LINE vs WhatsApp Chat Reader (Unofficial)
LINE is an MCP server published by line. 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
| Marketplace |  LINE |  WhatsApp Chat Reader (Unofficial) |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:2fe78452545d Forks (GitHub): 156 Pulls (Docker Hub): 24 812 Stars (Docker Hub): 0 Stars (GitHub): 788 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
| Fact | LINE | WhatsApp Chat Reader (Unofficial) |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 788 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 24 812 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 156 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/line) | On your machine (wa-chat-reader) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 5, secrets among them: 0 |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/line/line-bot-mcp-server | github.com/nabheetcloud/wa-chat-reader |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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
LINE
MCP server that integrates the LINE Messaging API to connect an AI Agent to the LINE Official Account.
WhatsApp Chat Reader (Unofficial)
Unofficial read-only MCP server for your local WhatsApp chat history (stays on your machine).
How to run each
LINE As a local MCP server: Docker image
claude mcp add --env "CHANNEL_ACCESS_TOKEN=<YOUR_CHANNEL_ACCESS_TOKEN>" --transport stdio line -- docker run -i --rm -e CHANNEL_ACCESS_TOKEN mcp/lineRequires: CHANNEL_ACCESS_TOKEN (secret)
WhatsApp Chat Reader (Unofficial) As a local MCP server: PyPI package
claude mcp add --transport stdio wa-chat-reader -- uvx wa-chat-readerCommands 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 LINE asks for
CHANNEL_ACCESS_TOKEN (secret)DESTINATION_USER_ID
Only WhatsApp Chat Reader (Unofficial) asks for
WHATSAPP_BACKUP_PATHSWHATSAPP_DB_PATHSWHATSAPP_DEBUGWHATSAPP_LOG_FILEWHATSAPP_MAX_DAYS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: LINE · 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.