Ext Ops Panel
Open dashboard
Comparison

spoki vs dev.wagate/wagate

spoki is a plugin bundle for AI coding tools published by Spoki-App. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). dev.wagate/wagate is an MCP server published by wagate.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
Marketplacespokidev.wagate/wagate
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.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

spoki vs dev.wagate/wagate
Factspokidev.wagate/wagate
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 bundleOn your machine (@wagate/mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 14, secrets among them: 1
Hooks it runs (differs)1Not published
Parts of the bundle (differs)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/spoki-app/spoki-claude-pluginNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-10-21

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

spoki

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

Connect your WhatsApp Business to Claude. Spoki lets you send messages, manage contacts, launch marketing campaigns, build automations, and track performance... all through natural conversation. You can go from "send a birthday coupon to my VIP list" to done in seconds. No dashboard switching, no manual exports. Just ask Claude.

dev.wagate/wagate

In its own words, on Official MCP Registry:

Read WhatsApp chats and groups, and send messages when allowed, through the WaGate API.

How to run each

spoki As a Claude Code plugin

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

dev.wagate/wagate As a local MCP server: npm package

Claude Code
claude mcp add --env "GATEWAY_API_TOKEN=<YOUR_GATEWAY_API_TOKEN>" --env "GATEWAY_CHANNEL_ID=<YOUR_GATEWAY_CHANNEL_ID>" --transport stdio wagate -- npx -y @wagate/mcp

Requires: GATEWAY_API_TOKEN (secret), GATEWAY_CHANNEL_ID

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only spoki asks for

  • SPOKI_API_KEY (secret)
  • SPOKI_BASE_URL

Only dev.wagate/wagate asks for

  • GATEWAY_ALLOW_SEND
  • GATEWAY_API_TOKEN (secret)
  • GATEWAY_API_URL
  • GATEWAY_CHANNEL_ID

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

What it can do: spoki · What it can do: dev.wagate/wagate · 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