Ext Ops Panel
Open dashboard
Comparison

XCP-ng AIops vs Arm MCP Server

XCP-ng AIops is an MCP server published by AIops-tools. Marketplaces we read that list it: 1 (Official MCP Registry). Arm MCP Server is an MCP server published by arm. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-25. 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
MarketplaceXCP-ng AIopsArm MCP Server
Official MCP Registry Listed
Version: 0.10.0
Downloads/month (PyPI): 954
Downloads/week (PyPI): 183
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.4.0
Forks (GitHub): 22
Stars (GitHub): 95
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:ea7c4d1daeb9
Forks (GitHub): 22
Stars (GitHub): 95
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

XCP-ng AIops vs Arm MCP Server
FactXCP-ng AIopsArm MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)95 (better)
Forks (GitHub) (differs)0 (worse)22 (better)
Last release (differs)2026-10-15Not published
Where it runs (differs)On your machine (xcpng-aiops)On your machine (docker.io/armlimited/arm-mcp:2.4.0)
Transportstdiostdio
Tools it declares (differs)Not published7
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/aiops-tools/xcpng-aiopsgithub.com/arm/mcp
Changes in the last 7 days00
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

XCP-ng AIops

In its own words, on Official MCP Registry:

Governed XCP-ng ops via Xen Orchestra — 29 MCP tools with audit, budget, undo guards.

Arm MCP Server

In its own words, on Official MCP Registry:

Official Arm MCP server for code migration, optimization, and Arm architecture guidance

How to run each

XCP-ng AIops As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio xcpng-aiops -- uvx xcpng-aiops

Arm MCP Server As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio arm-mcp -- docker run -i --rm run --rm -i -v "<YOUR_WORKSPACE_PATH>:/workspace" -v "<YOUR_SSH_PRIVATE_KEY_PATH>:/run/keys/ssh-key.pem:ro" -v "<YOUR_SSH_KNOWN_HOSTS_PATH>:/run/keys/known_hosts:ro" docker.io/armlimited/arm-mcp:2.4.0

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of XCP-ng AIops publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: XCP-ng AIops · What it can do: Arm MCP Server · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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