Ext Ops Panel
Open dashboard
Comparison

wu-whatsapp vs io.github.singleflo/evolution-api-mcp

wu-whatsapp is a plugin bundle for AI coding tools published by ibrahimhajjaj. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.singleflo/evolution-api-mcp is an MCP server published by singleflo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplacewu-whatsappio.github.singleflo/evolution-api-mcp
Claude Code: claude-plugins-community Listed
Version: 0.1.16
Forks (GitHub): 3
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (PyPI): 0
Downloads/week (PyPI): 151
Forks (GitHub): 0
Stars (GitHub): 0
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

wu-whatsapp vs io.github.singleflo/evolution-api-mcp
Factwu-whatsappio.github.singleflo/evolution-api-mcp
Marketplaces that list it11
Stars (GitHub) (differs)14 (better)0 (worse)
Forks (GitHub) (differs)3 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (evolution-mcp.singleflo.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published11, secrets among them: 1
Parts of the bundle (differs)15Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/ibrahimhajjaj/wu-cligithub.com/singleflo/evolution-api-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 24 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

wu-whatsapp

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

WhatsApp integration for Claude Code — send messages, search chats, manage groups via wu-cli

io.github.singleflo/evolution-api-mcp

In its own words, on Official MCP Registry:

Operate one Evolution API (WhatsApp) instance: chats, history, sending, groups, settings.

How to run each

wu-whatsapp As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install wu-whatsapp@claude-community

io.github.singleflo/evolution-api-mcp As a remote MCP server

Claude Code
claude mcp add --transport http evolution-api-mcp https://evolution-mcp.singleflo.com/mcp

Requires: EVOLUTION_API_URL, EVOLUTION_INSTANCE_TOKEN (secret)

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

Only io.github.singleflo/evolution-api-mcp 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

The marketplaces of wu-whatsapp publish no settings it asks for, so we do not compare settings.

What it can do: wu-whatsapp · What it can do: io.github.singleflo/evolution-api-mcp · 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