Ext Ops Panel
Open dashboard
Comparison

cc-wechat vs whatsapi.sh

cc-wechat is a plugin bundle for AI coding tools published by uetuluk. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). whatsapi.sh is an MCP server published by whatsapi.sh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplacecc-wechatwhatsapi.sh
Claude Code: claude-plugins-community Listed
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

cc-wechat vs whatsapi.sh
Factcc-wechatwhatsapi.sh
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.whatsapi.sh/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/uetuluk/cc-wechatNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-17
Endpoint at the last check (differs)no remote endpoint we checkResponded 36 h ago, requires a key

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

cc-wechat

In its own words, on Claude Code: claude-plugins-community:

WeChat channel for Claude Code — bridges your personal WeChat account to a Claude Code session via Tencent's iLink bot API. Supports two-way messaging (receive WeChat messages, reply from Claude Code) and permission relay (approve/deny tool use from your phone). QR code login via MCP elicitation, sender allowlist for security, and cursor persistence across reconnects.

whatsapi.sh

In its own words, on Official MCP Registry:

Send WhatsApp messages from your own numbers, read and answer chats, and send sign-in codes.

How to run each

cc-wechat As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install cc-wechat@claude-community

whatsapi.sh As a remote MCP server

Claude Code
claude mcp add --transport http whatsapi https://api.whatsapi.sh/mcp

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

Only whatsapi.sh 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

Neither one's marketplaces publish the settings it asks for.

What it can do: cc-wechat · What it can do: whatsapi.sh · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built