WhatsApp Channel for Claude Code vs uni-msg WhatsApp
WhatsApp Channel for Claude Code is a plugin bundle for AI coding tools published by Rich627. Marketplaces we read that list it: 1 (Community GitHub marketplaces). uni-msg WhatsApp is an MCP server published by uni-msg.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 | ||
|---|---|---|
| Community marketplace rich627/whatsapp-claude-plugin | Listed Version: 0.33.1 Forks (GitHub): 35 Stars (GitHub): 118 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.1 Downloads/month (npm): 110 Downloads/week (npm): 41 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 | WhatsApp Channel for Claude Code | uni-msg WhatsApp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 118 | No figure on GitHub |
| Forks (GitHub) (differs) | 35 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (uni-msg.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 8, secrets among them: 5 | 1, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 6 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/rich627/whatsapp-claude-plugin | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-11-03 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 35 h ago returned HTTP 401 |
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
WhatsApp Channel for Claude Code
WhatsApp channel for Claude Code — linked device or official Cloud API, with pairing, allowlists and access control.
uni-msg WhatsApp
Drive WhatsApp from any MCP client: pair devices, send text and media, manage contacts and groups.
How to run each
WhatsApp Channel for Claude Code As a Claude Code plugin
/plugin marketplace add rich627/whatsapp-claude-plugin
/plugin install whatsapp-channel@whatsapp-claude-pluginuni-msg WhatsApp As a remote MCP server
claude mcp add --transport http whatsapp https://uni-msg.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: UNIMSG_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only uni-msg WhatsApp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only WhatsApp Channel for Claude Code asks for
WHATSAPP_CLOUD_ACCESS_TOKEN (secret)WHATSAPP_CLOUD_APP_SECRET (secret)WHATSAPP_CLOUD_PHONE_NUMBER_IDWHATSAPP_CLOUD_VERIFY_TOKEN (secret)WHATSAPP_GROQ_API_KEY (secret)WHATSAPP_OPENAI_API_KEY (secret)WHATSAPP_PROVIDERWHATSAPP_TRANSCRIPTION_PROVIDER
Only uni-msg WhatsApp asks for
UNIMSG_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: WhatsApp Channel for Claude Code · What it can do: uni-msg WhatsApp · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.