Ext Ops Panel
Open dashboard
Comparison

io.github.WaterTian/wechat-devtools vs io.github.mrfentmen/whiley-mcp

io.github.WaterTian/wechat-devtools is an MCP server published by WaterTian. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). io.github.mrfentmen/whiley-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
Marketplaceio.github.WaterTian/wechat-devtoolsio.github.mrfentmen/whiley-mcp
Official MCP Registry Listed
Version: 0.1.0
Downloads/month (PyPI): 1 288
Downloads/week (PyPI): 672
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
PyPI (MCP servers) Listed
Version: 0.9.20
Downloads/month (PyPI): 1 288
Downloads/week (PyPI): 672
Forks (GitHub): 16
Stars (GitHub): 164
Not marked · First seen
Not listed

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

io.github.WaterTian/wechat-devtools vs io.github.mrfentmen/whiley-mcp
Factio.github.WaterTian/wechat-devtoolsio.github.mrfentmen/whiley-mcp
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)164 (better)0 (worse)
Forks (GitHub) (differs)16 (better)0 (worse)
Last release (differs)2026-10-26Not published
Where it runs (differs)On your machine (wechat-devtools-mcp)On your machine (@mrfentmen/whiley-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)6, secrets among them: 0Not published
Licence (differs)MITNot stated
Repository (differs)github.com/watertian/wechat-devtoolsgithub.com/mrfentmen/awesome-servers
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-08

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

io.github.WaterTian/wechat-devtools

In its own words, on Official MCP Registry:

MCP Server for WeChat DevTools CLI - Automate Mini Program development & testing.

io.github.mrfentmen/whiley-mcp

In its own words, on Official MCP Registry:

Whiley MCP: 20 real tools to read, check, lint, scaffold, build and run Whiley code.

How to run each

io.github.WaterTian/wechat-devtools As a local MCP server: PyPI package

Claude Code
claude mcp add --env "WECHAT_DEVTOOLS_CLI=<YOUR_WECHAT_DEVTOOLS_CLI>" --env "WECHAT_PROJECT_PATH=<YOUR_WECHAT_PROJECT_PATH>" --transport stdio wechat-devtools -- uvx wechat-devtools-mcp

Requires: WECHAT_DEVTOOLS_CLI, WECHAT_PROJECT_PATH

io.github.mrfentmen/whiley-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio whiley-mcp -- npx -y @mrfentmen/whiley-mcp

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

The marketplaces of io.github.mrfentmen/whiley-mcp publish no settings it asks for, so we do not compare settings.

What it can do: io.github.WaterTian/wechat-devtools · What it can do: io.github.mrfentmen/whiley-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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