Ext Ops Panel
Open dashboard
Comparison

SuperOps vs io.github.levelsofself/ai-ops

SuperOps is an MCP server published by WYRE-AI. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.levelsofself/ai-ops is an MCP server published by levelsofself. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceSuperOpsio.github.levelsofself/ai-ops
Official MCP Registry Listed
Version: 2.0.4
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 1.0.1
Downloads/month (npm): 181
Downloads/week (npm): 38
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

SuperOps vs io.github.levelsofself/ai-ops
FactSuperOpsio.github.levelsofself/ai-ops
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)2026-10-14Not published
Where it runs (differs)On your machine (ghcr.io/wyre-ai/superops-mcp:v2.0.4)On your machine (palyan-ai-ops-mcp-server)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)6, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/wyre-ai/superops-mcpgithub.com/levelsofself/mcp-ops-server
Changes in the last 7 days (differs)20
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

SuperOps

In its own words, on Official MCP Registry:

MCP server for SuperOps unified PSA+RMM — clients, tickets, assets, and more.

io.github.levelsofself/ai-ops

In its own words, on Official MCP Registry:

AI operations management: 12 specialized agents, task dispatch, and team coordination.

How to run each

SuperOps As a local MCP server: Docker image

Claude Code
claude mcp add --env "SUPEROPS_API_TOKEN=<YOUR_SUPEROPS_API_TOKEN>" --env "SUPEROPS_SUBDOMAIN=<YOUR_SUPEROPS_SUBDOMAIN>" --transport stdio superops-mcp -- docker run -i --rm -e SUPEROPS_API_TOKEN -e SUPEROPS_SUBDOMAIN ghcr.io/wyre-ai/superops-mcp:v2.0.4

Requires: SUPEROPS_API_TOKEN (secret), SUPEROPS_SUBDOMAIN

io.github.levelsofself/ai-ops As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ai-ops -- npx -y palyan-ai-ops-mcp-server

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

What it can do: SuperOps · What it can do: io.github.levelsofself/ai-ops · Compare two other plugins

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