Ext Ops Panel
Open dashboard
Comparison

Inspektor Gadget vs Proxmox VE

Inspektor Gadget is an MCP server published by inspektor-gadget. Marketplaces we read that list it: 1 (Docker MCP Catalog). Proxmox VE is an MCP server published by mattoddie. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
MarketplaceInspektor GadgetProxmox VE
Docker MCP Catalog Listed
Version: sha256:a54c99a50a81
Forks (GitHub): 6
Pulls (Docker Hub): 13 923
Stars (Docker Hub): 2
Stars (GitHub): 28
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.1
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

Inspektor Gadget vs Proxmox VE
FactInspektor GadgetProxmox VE
Marketplaces that list it11
Stars (GitHub) (differs)28 (better)1 (worse)
Pulls (Docker Hub) (differs)13 923No figure on Docker Hub
Forks (GitHub) (differs)6 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/inspektor-gadget)On your machine (ghcr.io/mattoddie/proxmox-mcp:0.5.1)
Transportstdiostdio
Tools it declares (differs)37Not published
Environment variables it asks for (differs)Not published13, secrets among them: 2
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/inspektor-gadget/ig-mcp-servergithub.com/mattoddie/proxmox-mcp
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-22

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

Inspektor Gadget

In its own words, on Docker MCP Catalog:

AI interface to troubleshoot and observe Kubernetes/Container workloads.

Proxmox VE

In its own words, on Official MCP Registry:

Monitor and manage Proxmox VE clusters: VMs, containers, storage and backups. Read-only by default.

How to run each

Inspektor Gadget As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio inspektor-gadget -- docker run -i --rm mcp/inspektor-gadget

Proxmox VE As a local MCP server: Docker image

Claude Code
claude mcp add --env "PROXMOX_API_TOKEN=<YOUR_PROXMOX_API_TOKEN>" --env "PROXMOX_PASSWORD=<YOUR_PROXMOX_PASSWORD>" --env "PROXMOX_URL=<YOUR_PROXMOX_URL>" --transport stdio proxmox-mcp -- docker run -i --rm -e PROXMOX_API_TOKEN -e PROXMOX_PASSWORD -e PROXMOX_URL ghcr.io/mattoddie/proxmox-mcp:0.5.1

Requires: PROXMOX_API_TOKEN (secret), PROXMOX_PASSWORD (secret), PROXMOX_URL

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

Tools each declares

The marketplaces of Proxmox VE publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Inspektor Gadget publish no settings it asks for, so we do not compare settings.

What it can do: Inspektor Gadget · What it can do: Proxmox VE · 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