Ext Ops Panel
Open dashboard
Comparison

unifi-mcp vs io.github.us-all/unifi

unifi-mcp is a plugin bundle for AI coding tools published by jmagar. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.us-all/unifi is an MCP server published by us-all. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplaceunifi-mcpio.github.us-all/unifi
Community marketplace jmagar/claude-homelab Listed
Version: 1.0.0
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.13.3
Downloads/month (npm): 399
Downloads/week (npm): 47
Forks (GitHub): 1
Stars (GitHub): 3
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

unifi-mcp vs io.github.us-all/unifi
Factunifi-mcpio.github.us-all/unifi
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub3
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@us-all/unifi-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published10, secrets among them: 3
LicenceNot statedNot stated
Repository (differs)github.com/jmagar/unifi-mcpgithub.com/us-all/unifi-mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-10-232026-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

unifi-mcp

In its own words, on Community GitHub marketplaces:

UniFi network management via MCP tools. Monitor devices, clients, network health, firewall rules, and perform management operations.

io.github.us-all/unifi

In its own words, on Official MCP Registry:

UniFi semantic-analysis MCP — fleet health, anomaly detection, cross-site analytics

How to run each

unifi-mcp As a Claude Code plugin

Claude Code
/plugin marketplace add jmagar/claude-homelab
/plugin install unifi-mcp@claude-homelab

io.github.us-all/unifi As a local MCP server: npm package

Claude Code
claude mcp add --env "UNIFI_API_KEY=<YOUR_UNIFI_API_KEY>" --env "UNIFI_API_KEY_OWNER=<YOUR_UNIFI_API_KEY_OWNER>" --env "UNIFI_LOCAL_PASS=<YOUR_UNIFI_LOCAL_PASS>" --transport stdio unifi -- npx -y @us-all/unifi-mcp

Requires: UNIFI_API_KEY (secret), UNIFI_API_KEY_OWNER (secret), UNIFI_LOCAL_PASS (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 unifi-mcp publish no settings it asks for, so we do not compare settings.

What it can do: unifi-mcp · What it can do: io.github.us-all/unifi · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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