Ext Ops Panel
Open dashboard
Comparison

sysadmin vs ultranix-mcp

sysadmin is a plugin bundle for AI coding tools published by 2389-research. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ultranix-mcp is an MCP server published by jxoesneon. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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
Marketplacesysadminultranix-mcp
Claude Code: claude-plugins-community Listed
Version: dbb92f1
Forks (GitHub): 9
Stars (GitHub): 102
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.4.0
Forks (GitHub): 1
Stars (GitHub): 1
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

sysadmin vs ultranix-mcp
Factsysadminultranix-mcp
Marketplaces that list it11
Stars (GitHub) (differs)102 (better)1 (worse)
Forks (GitHub) (differs)9 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ghcr.io/jxoesneon/ultranix-mcp:1.4.0)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published6, secrets among them: 4
LicenceNot statedNot stated
Repository (differs)github.com/2389-research/claude-pluginsgithub.com/jxoesneon/ultranix-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

sysadmin

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

[meta] system administration: structured Linux maintenance and diagnostics

ultranix-mcp

In its own words, on Official MCP Registry:

Secure Linux desktop automation - input, screen/OCR/vision, AT-SPI2 UI tree, window, clipboard

How to run each

sysadmin As a Claude Code plugin

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

ultranix-mcp As a local MCP server: Docker image

Claude Code
claude mcp add --env "ULTRANIX_MCP_API_KEY=<YOUR_ULTRANIX_MCP_API_KEY>" --env "ULTRANIX_MCP_AUDIT_SECRET=<YOUR_ULTRANIX_MCP_AUDIT_SECRET>" --env "ULTRANIX_MCP_HISTORY_SECRET=<YOUR_ULTRANIX_MCP_HISTORY_SECRET>" --env "ULTRANIX_MCP_SENTRY_DSN=<YOUR_ULTRANIX_MCP_SENTRY_DSN>" --transport stdio ultranix-mcp -- docker run -i --rm -e ULTRANIX_MCP_API_KEY -e ULTRANIX_MCP_AUDIT_SECRET -e ULTRANIX_MCP_HISTORY_SECRET -e ULTRANIX_MCP_SENTRY_DSN ghcr.io/jxoesneon/ultranix-mcp:1.4.0

Requires: ULTRANIX_MCP_API_KEY (secret), ULTRANIX_MCP_AUDIT_SECRET (secret), ULTRANIX_MCP_HISTORY_SECRET (secret), ULTRANIX_MCP_SENTRY_DSN (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 sysadmin publish no settings it asks for, so we do not compare settings.

What it can do: sysadmin · What it can do: ultranix-mcp · 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