Ext Ops Panel
Open dashboard
Comparison

io.github.apiarya/wemo vs io.github.chrischall/simplisafe-mcp

io.github.apiarya/wemo is an MCP server published by apiarya. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.chrischall/simplisafe-mcp is an MCP server published by chrischall. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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.apiarya/wemoio.github.chrischall/simplisafe-mcp
Official MCP Registry Listed
Version: 1.4.1
Downloads/month (PyPI): 214
Downloads/week (PyPI): 67
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.3.2
Downloads/month (npm): 2 796
Downloads/week (npm): 719
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

io.github.apiarya/wemo vs io.github.chrischall/simplisafe-mcp
Factio.github.apiarya/wemoio.github.chrischall/simplisafe-mcp
Marketplaces that list it11
Stars (GitHub) (differs)54 (better)0 (worse)
Forks (GitHub) (differs)7 (better)0 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (wemo-mcp-server)On your machine (simplisafe-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/apiarya/wemo-mcp-servergithub.com/chrischall/simplisafe-mcp
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11

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.apiarya/wemo

In its own words, on Official MCP Registry:

Control WeMo smart home devices - discover, toggle, adjust brightness, and manage HomeKit codes

io.github.chrischall/simplisafe-mcp

In its own words, on Official MCP Registry:

Check SimpliSafe system state and sensors, review events, arm/disarm, and control smart locks

How to run each

io.github.apiarya/wemo As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio wemo -- uvx wemo-mcp-server

io.github.chrischall/simplisafe-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "SIMPLISAFE_REFRESH_TOKEN=<YOUR_SIMPLISAFE_REFRESH_TOKEN>" --transport stdio simplisafe-mcp -- npx -y simplisafe-mcp

Requires: SIMPLISAFE_REFRESH_TOKEN (secret)

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.apiarya/wemo publish no settings it asks for, so we do not compare settings.

What it can do: io.github.apiarya/wemo · What it can do: io.github.chrischall/simplisafe-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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