Ext Ops Panel
Open dashboard
Comparison

wecom vs io.github.conquext/neuron

wecom is a plugin bundle for AI coding tools published by yangsjt. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.conquext/neuron is an MCP server published by conquext. 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
Marketplacewecomio.github.conquext/neuron
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Downloads/month (npm): 198
Downloads/week (npm): 8
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

wecom vs io.github.conquext/neuron
Factwecomio.github.conquext/neuron
Marketplaces that list it11
Stars (GitHub) (differs)2No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.neuron.ng/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/yangsjt/claude-channel-wecomgithub.com/conquext/neuron
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 400 (2 days ago)

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

wecom

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

WeCom (Enterprise WeChat) Channel Plugin for Claude Code — enables two-way messaging between Claude Code sessions and WeCom users via AI Bot or Self-built App mode.

io.github.conquext/neuron

In its own words, on Official MCP Registry:

AI-powered WhatsApp chatbot platform with 196 tools for bots, campaigns, and contacts.

How to run each

wecom As a Claude Code plugin

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

io.github.conquext/neuron As a remote MCP server

Claude Code
claude mcp add --transport http neuron https://mcp.neuron.ng/mcp

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

Only io.github.conquext/neuron 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: wecom · What it can do: io.github.conquext/neuron · 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