Ext Ops Panel
Open dashboard
Comparison

Proxmox VE vs Lium GPU Cloud

Proxmox VE is an MCP server published by GethosTheWalrus. Marketplaces we read that list it: 1 (Docker MCP Catalog). Lium GPU Cloud is an MCP server published by Datura-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
MarketplaceProxmox VELium GPU Cloud
Docker MCP Catalog Listed
Version: sha256:6e30b4d837b2
Forks (GitHub): 16
Pulls (Docker Hub): 35 169
Stars (Docker Hub): 3
Stars (GitHub): 214
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.26.0
Forks (GitHub): 3
Stars (GitHub): 7
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

Proxmox VE vs Lium GPU Cloud
FactProxmox VELium GPU Cloud
Marketplaces that list it11
Stars (GitHub) (differs)214 (better)7 (worse)
Pulls (Docker Hub) (differs)35 169No figure on Docker Hub
Forks (GitHub) (differs)16 (better)3 (worse)
Last release (differs)Not published2026-10-21
Where it runs (differs)On your machine (mcp/proxmox)On your machine (lium.io)
Transportstdiostdio
Tools it declares (differs)286Not published
Environment variables it asks for (differs)8, secrets among them: 21, secrets among them: 1
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/gethosthewalrus/proxmox-mcpgithub.com/datura-ai/lium
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-20

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

Proxmox VE

In its own words, on Docker MCP Catalog:

Manage Proxmox VE infrastructure including virtual machines, containers, storage, networking, firewall rules, high availability, and more.

Lium GPU Cloud

In its own words, on Official MCP Registry:

Rent NVIDIA GPU pods on Lium, run commands on them and remove them, billed per second.

How to run each

Proxmox VE As a local MCP server: Docker image

Claude Code
claude mcp add --env "PROXMOX_PASSWORD=<YOUR_PROXMOX_PASSWORD>" --env "PROXMOX_TOKEN_VALUE=<YOUR_PROXMOX_TOKEN_VALUE>" --transport stdio proxmox -- docker run -i --rm -e PROXMOX_PASSWORD -e PROXMOX_TOKEN_VALUE mcp/proxmox

Requires: PROXMOX_PASSWORD (secret), PROXMOX_TOKEN_VALUE (secret)

Lium GPU Cloud As a local MCP server: PyPI package

Claude Code
claude mcp add --env "LIUM_API_KEY=<YOUR_LIUM_API_KEY>" --transport stdio lium -- uvx --from "lium.io[mcp]" lium.io mcp

Requires: LIUM_API_KEY (secret)

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

Tools each declares

The marketplaces of Lium GPU Cloud publish no list of tools, so we do not compare tools.

Settings each asks for

Only Proxmox VE asks for

  • PROXMOX_HOST
  • PROXMOX_PASSWORD (secret)
  • PROXMOX_PORT
  • PROXMOX_TIMEOUT
  • PROXMOX_TOKEN_NAME
  • PROXMOX_TOKEN_VALUE (secret)
  • PROXMOX_USER
  • PROXMOX_VERIFY_SSL

Only Lium GPU Cloud asks for

  • LIUM_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Proxmox VE · What it can do: Lium GPU Cloud · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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