Server providing Argo CD integration for MCP clients.
Nothing to run from here
Proxmox VE is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
154
tools declared
—
trust score
local
runs on your machine
—
calls last 7d
What it does
Monitor and manage Proxmox VE clusters: VMs, containers, storage and backups. Read-only by default.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'PROXMOX_URL=${PROXMOX_URL}' --transport stdio mattoddie-proxmox-ve-mcp '--' docker run -i --rm -e PROXMOX_URL ghcr.io/mattoddie/proxmox-mcp:0.5.1
# 2 — ask your agent for something these tools do
# proxmox_check_ceph_safety, proxmox_check_container_feature, proxmox_check_container_migration and 151 more
It needs PROXMOX_URL: this reads it from your environment, so export it first.
Proxmox VE costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MAAll 6 servers
mattoddie6 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Proxmox VE as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It has not been scanned here, so read the surface, and its source, before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Docker installed and running. Only the required variables are passed into the container. To set an optional one (MCP_TRANSPORT, PROXMOX_API_TOKEN, PROXMOX_USERNAME, PROXMOX_PASSWORD, PROXMOX_TLS_FINGERPRINT, PROXMOX_VERIFY_SSL and 6 more), add -e NAME before the image name and give it a value in the entry’s env: an unset -e would clear the default the image sets. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads PROXMOX_URL (Address of any node in the cluster, with the port) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx PROXMOX_URL … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'PROXMOX_URL=${PROXMOX_URL}' --transport stdio mattoddie-proxmox-ve-mcp '--' docker run -i --rm -e PROXMOX_URL ghcr.io/mattoddie/proxmox-mcp:0.5.1Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own image: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs settings only you can give it: PROXMOX_URL — Address of any node in the cluster, with the port.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
154 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Ask Ceph whether stopping or destroying an OSD, monitor or MDS is safe right now (e.g. no PGs would become unavailable). Call before proxmox_delete_ceph_osd, proxmox_delete_ceph_service or stopping services.
No parameter schema on file.
Check whether a container's storage supports snapshots, cloning (linked) or copying (full clone), optionally from a given snapshot, and on which nodes. Useful before proxmox_create_snapshot or proxmox_clone_container.
No parameter schema on file.
Check whether an LXC container can be migrated, and to which nodes: reports running state, local disks/mount points that block migration, and allowed/not-allowed target nodes. Call before proxmox_migrate_container.
No parameter schema on file.
Check whether a VM's storage supports snapshots, linked clones ('clone') or full copies ('copy'), optionally for a given snapshot, and on which nodes. Useful before proxmox_clone_vm or taking snapshots.
No parameter schema on file.
Check whether and where a VM can be migrated before calling proxmox_migrate_vm: allowed and blocked target nodes (with unavailable storages or blocking HA rules), local disks that would need with_local_disks/targetstorage, local devices (PCI/USB passthrough) that block migration, and mapped…
No parameter schema on file.
Get an ACME account's details: CA directory, account URL (location), status, contacts and accepted terms of service. Keys are redacted.
No parameter schema on file.
Show which credential fields each ACME DNS API plugin needs (e.g. CF_Token for Cloudflare), to fill data in proxmox_save_acme_plugin. Filter by api name.
No parameter schema on file.
Get one ACME challenge plugin's configuration (DNS API, nodes, validation delay). Credential values are redacted.
No parameter schema on file.
Get one API token's settings (privilege separation, expiry, comment) and, when privilege-separated, its own ACL entries.
No parameter schema on file.
Show the guest configuration stored inside a backup archive (cores, memory, disks, network...) without restoring it, e.g. to check what a backup contains or which storage its disks need. Secrets are redacted.
No parameter schema on file.
Get one backup job's settings plus the guests it currently includes and, per guest, which disks are backed up (and why others are excluded, e.g. backup=0).
No parameter schema on file.
Read Ceph configuration: the configuration database (ceph config dump: section, name, value) and/or the ceph.conf file. Secrets such as keys are redacted.
No parameter schema on file.
Get the decompiled CRUSH map (devices, buckets, rules) and the list of CRUSH rule names usable as a pool's crush_rule.
No parameter schema on file.
Show which cluster-wide Ceph OSD flags are set (noout, noscrub, nodeep-scrub, norebalance, pause...). Change them with proxmox_set_ceph_flags.
No parameter schema on file.
Read lines of the Ceph cluster log (ceph.log) from a node: health changes, OSD up/down events, slow ops and scrub errors.
No parameter schema on file.
Get metadata of every Ceph daemon (mon, mgr, mds, osd) and node: host, Ceph version and release, memory. Useful to spot daemons running an outdated version after an upgrade.
No parameter schema on file.
Get one OSD's details: daemon metadata (devices, BlueStore, memory, version) and its logical volume info (block/DB/WAL devices).
No parameter schema on file.
Get one Ceph pool's settings (size, min_size, PGs, autoscaler, CRUSH rule, application, protection flags) and, with statistics=true, its usage and I/O statistics.
No parameter schema on file.
Summarized Ceph cluster health: HEALTH_OK/WARN/ERR with each health check, monitor quorum, active/standby managers, OSD counts (up/in/down), PG states, raw usage and client I/O. Start here for any Ceph question; drill down with proxmox_list_ceph_osds, proxmox_list_ceph_pools or…
No parameter schema on file.
Get the corosync cluster configuration: member nodes with their IDs, votes and link addresses, the totem settings, and the join information (fingerprint, addresses) used to add nodes.
No parameter schema on file.
Read recent entries of the cluster log (task starts/ends, logins and other cluster events from all nodes).
No parameter schema on file.
Get datacenter-wide options (datacenter.cfg): keyboard, console, migration network/type, HA shutdown policy, bandwidth limits, MAC prefix, tag style, next-id range and more.
No parameter schema on file.
One-call overview of the whole cluster: name, quorum, Proxmox version, every node (online state, CPU, memory, uptime), guest counts by state, totals, storage usage and HA state. A good first call.
No parameter schema on file.
Get an LXC container's live status (CPU, memory, swap, rootfs usage, uptime) together with a summary of its configuration: hostname, OS, cores, memory, swap, rootfs and mount points, network interfaces with configured IPs, live IP addresses (when running), features, unprivileged, onboot, tags and…
No parameter schema on file.
Get an LXC container's full configuration as stored by Proxmox (secrets redacted). Options: current=true for the running values instead of pending ones, snapshot to read the config as saved in a snapshot, or pending=true to list each key with its current and pending value. The returned digest can…
No parameter schema on file.
Get the live network interfaces and IP addresses (IPv4 and IPv6) inside a running LXC container, including addresses obtained via DHCP/SLAAC that the config doesn't show. The container must be running.
No parameter schema on file.
Summarize an LXC container's performance history from RRD data: average, maximum and latest CPU %, memory, swap, disk usage, network and disk I/O rates over the chosen timeframe. Set points=true to also get the individual data points.
No parameter schema on file.
Get one custom CPU model definition, including its digest.
No parameter schema on file.
Get a disk's SMART health and attributes (ATA attribute table, or the text report for NVMe/SAS).
No parameter schema on file.
Read the firewall log of a node (all its traffic, including guests on it) or of one guest. Only packets matching rules/policies with a log level other than nolog are logged; set log_level_in on the options or log on a rule to see drops.
No parameter schema on file.
Get firewall options for the datacenter (enable, default policies, ebtables, log rate limit), a node (enable, nftables, conntrack, synflood/smurf/tcpflags protection, log levels) or a guest (enable, policies, MAC/IP filter, DHCP, NDP, RA, log levels). effective fills in Proxmox's defaults for…
No parameter schema on file.
Get one firewall rule by position at any level (cluster, node, guest or security group), with its digest for safe updates.
No parameter schema on file.
Get a group's members and comment.
No parameter schema on file.
List a running VM's mounted filesystems from inside the guest (QEMU guest agent get-fsinfo): mountpoint, type, used/total space and backing disks. Use it to check real disk usage inside a VM (Proxmox's own disk figures for VMs are not filesystem usage). VMs only.
No parameter schema on file.
Whole-picture firewall view for one VM/container, for questions like 'why can't I reach VM X': whether the firewall is enabled at datacenter, node and guest level and on each NIC (firewall=1), the effective policies, the guest's rules (one line each), IP/MAC filters, and plain-language findings…
No parameter schema on file.
Ask a running VM's QEMU guest agent about the guest: OS name/version/kernel, hostname, timezone, guest clock (and its skew from this server), vCPUs online and the agent version with its disabled commands. VMs only (containers need no agent). Individual queries that fail are reported under errors…
No parameter schema on file.
Show a running VM's memory blocks as the guest sees them (QEMU guest agent get-memory-blocks/get-memory-block-info): block size and how many blocks/how much memory is online. Useful after memory hotplug. VMs only; not all guest OSes support it.
No parameter schema on file.
List a running VM's network interfaces as seen inside the guest (via the QEMU guest agent): name, MAC, IPv4/IPv6 addresses with prefix, and traffic counters. The reliable way to find a VM's IP address. Loopback is hidden unless include_loopback=true. VMs only; for containers use…
No parameter schema on file.
List the users currently logged in to a running VM (QEMU guest agent get-users), with domain and login time. VMs only.
No parameter schema on file.
Get one HA group's configuration (PVE 8; deprecated in PVE 9 in favour of HA rules).
No parameter schema on file.
Get one HA resource's configuration, its current status, and the HA rules that reference it (PVE 9+).
No parameter schema on file.
Get one HA rule (PVE 9+) with its digest.
No parameter schema on file.
High-availability overview: quorum, the current CRM master, each node's LRM state (active/idle/maintenance, last update), fencing/arming state (PVE 9.1+), and every HA-managed service with its node and state. Use proxmox_list_ha_resources for the configured settings.
No parameter schema on file.
Get the next free VM/container ID, or check whether a specific ID is free.
No parameter schema on file.
Get what a node's QEMU supports for VM configuration: CPU models (built-in and custom), machine types/versions (q35, i440fx) and the VM-specific CPU flags that can be toggled. Use it to pick valid values for a VM's cpu/machine options.
No parameter schema on file.
List the TLS certificates of a node's web interface/API (pve-root-ca, pve-ssl and any custom or ACME pveproxy-ssl certificate) with subject, issuer, SANs, validity, days left and fingerprint. Private keys are never returned.
No parameter schema on file.
Get a node's own options (/etc/pve/nodes/<node>/config): notes/description, wake-on-LAN MAC, ACME account and domains, start-on-boot delay, ballooning target and location, plus the digest for safe updates.
No parameter schema on file.
Get a node's DNS resolver settings: search domain and up to three name servers.
No parameter schema on file.
Read a node's /etc/hosts file and its digest (pass the digest to proxmox_set_node_hosts to avoid overwriting concurrent edits).
No parameter schema on file.
Read a node's systemd journal: the last N entries (default 100) or a time range, optionally only one unit, a syslog identifier, a priority level or kernel messages.
No parameter schema on file.
Traffic counters of the guests' tap/veth network devices on a node (bytes in/out per device and VMID), as seen from the host.
No parameter schema on file.
Get the configuration of one network interface on a node (as stored in /etc/network/interfaces, including pending changes).
No parameter schema on file.
List the installed versions of the important Proxmox packages on a node (like pveversion -v), including the running kernel.
No parameter schema on file.
The node's pvereport: a long text dump of versions, hardware, storage, network, cluster and guest configuration, as used for support requests. Large; truncated to max_chars. Can take a while to generate.
No parameter schema on file.
Node performance history from the RRD database (CPU, IO wait, load, memory, swap, root disk, network, ARC...) over a timeframe, summarized as min/avg/max/last per metric plus a short downsampled series. Network values are bytes per second.
No parameter schema on file.
Detailed status of one node: CPU model/sockets/cores and usage, IO wait, load average, memory/swap/root filesystem usage, kernel, Proxmox VE version, boot mode (EFI/BIOS, secure boot), uptime, KSM sharing and the subscription status. Use proxmox_list_nodes for all nodes at a glance and…
No parameter schema on file.
Get a node's subscription status, level, product, sockets and next due date. The key itself is never shown.
No parameter schema on file.
Read a node's system log (journal rendered as syslog lines), optionally for one service and a time range. Page with start/limit. For the raw systemd journal with 'last N lines' semantics use proxmox_get_node_journal.
No parameter schema on file.
Get a node's current time (UTC), local time and configured time zone. Useful for spotting clock drift between nodes.
No parameter schema on file.
Get one notification endpoint's configuration. The type is looked up when omitted. Tokens, passwords and webhook secrets are redacted; webhook headers and body are shown decoded (credential-like headers redacted).
No parameter schema on file.
Get one notification matcher's rules and targets (plus its digest for safe updates).
No parameter schema on file.
List the metadata fields notifications carry (type, hostname, job-id...) and their known values, for writing match_field rules in proxmox_save_notification_matcher.
No parameter schema on file.
Get the changelog of a package available on a node, e.g. to see what an update to pve-manager or proxmox-kernel changes. Truncated to max_chars.
No parameter schema on file.
Show effective privileges per path for the API token/user this server uses (default) or for another user or token. The first thing to check when a tool fails with 403 / 'Permission check failed': it shows exactly which privileges are held where. Use path to check a single path such as /vms/100.
No parameter schema on file.
Get a resource pool's comment and members: guests (status, node, CPU/memory use) and storage (usage).
No parameter schema on file.
Get an authentication realm's configuration (servers, base DN, sync options, OpenID issuer...). Bind passwords and client keys are redacted.
No parameter schema on file.
Get one replication job's configuration (with digest for safe updates) and its current status on the source node.
No parameter schema on file.
Read the log of a replication job's last run from the source node, e.g. to diagnose a failing job.
No parameter schema on file.
Get one PCI, USB or directory resource mapping with its per-node entries and digest.
No parameter schema on file.
Get the privileges of one role, grouped by area (VM, Datastore, Sys...).
No parameter schema on file.
List the IP allocations recorded in an SDN IPAM (default the built-in 'pve' IPAM): IP, MAC, hostname, VMID, vnet/subnet and gateway entries. Use it to find which guest holds an address or which IPs are free. Related: proxmox_save_sdn_vnet_ip to add or change a mapping.
No parameter schema on file.
Get the full configuration of one SDN zone, vnet, subnet, controller, IPAM or DNS plugin, including its digest for optimistic locking. With pending=true, uncommitted changes are shown under pending.
No parameter schema on file.
Dry-run proxmox_apply_sdn for one node: shows the diff between the running and the pending network interfaces (/etc/network/interfaces.d/sdn) and FRR routing configuration. Use it to review staged SDN changes before applying them.
No parameter schema on file.
Show the live SDN state on nodes: each zone's status (available/pending/error) per node and the status of the vnets in it. Use it after proxmox_apply_sdn to confirm the configuration came up, or to find nodes where a zone is in error.
No parameter schema on file.
Get a snapshot of a VM or container: its description, time, parent, whether RAM was saved, and the guest configuration as it was at that snapshot (disks and networks summarized, secrets redacted). Useful to see what a rollback would restore.
No parameter schema on file.
Get one storage definition (full config, secrets redacted) and its status/usage on each node. Pass node for that node's detailed status (active, enabled, available bytes).
No parameter schema on file.
Summarize a storage's usage over time from its RRD data (current, min, max, growth over the period) with a few sample points. Useful for capacity planning.
No parameter schema on file.
Get a task's status (running/stopped), exit status and the last lines of its log.
No parameter schema on file.
Read a task's log, paging from the start (or the end with tail=true).
No parameter schema on file.
Get one user's configuration: enabled state, expiry, name, email, groups, comment, API tokens and TFA entries. For effective permissions use proxmox_get_permissions.
No parameter schema on file.
Get the Proxmox VE version and release of the API endpoint this server talks to.
No parameter schema on file.
Get a VM's live status (run state, CPU, memory, disk/network I/O, uptime, HA, lock, guest agent, QEMU version) together with a summary of its configuration (CPU, memory, disks, NICs, boot order, firmware, cloud-init, tags, notes) and any pending changes that need a restart. Use…
No parameter schema on file.
Show a VM's cloud-init settings with current vs pending values (pending ones need proxmox_regenerate_vm_cloudinit or a restart to reach the guest), plus the generated user-data, network-config and meta-data as the guest will see them. Passwords are redacted.
No parameter schema on file.
Get a VM's configuration as Proxmox stores it (key → value, secrets redacted). By default pending changes are shown applied; current=true shows the running values instead, pending=true lists every key with its current and pending value, and snapshot reads the config saved in a snapshot. The…
No parameter schema on file.
Get a VM's performance history from Proxmox's RRD database: min/avg/max of CPU %, memory, network and disk throughput and pressure stalls over the last hour/day/week/month/year, plus a downsampled time series. Use for 'was it busy?', trend and capacity questions.
No parameter schema on file.
Get a volume's attributes: path on disk, format, size, used space, notes and protection flag.
No parameter schema on file.
Show the vzdump defaults a node applies to backups (from /etc/vzdump.conf, merged with a storage's settings when storage is given): default storage, mode, compression, retention, bandwidth limits and so on.
No parameter schema on file.
Get a zpool's detailed status (like zpool status): state, status/action messages, last scrub/resilver, errors and the vdev tree with read/write/checksum error counters.
No parameter schema on file.
List access control entries: which role a user, group or API token has on which path (/, /vms/100, /storage/local, /pool/x, /nodes/pve1...) and whether it propagates to sub-paths. Filters combine. For what a user can effectively do, use proxmox_get_permissions.
No parameter schema on file.
List the cluster's registered ACME accounts (used to order node certificates), with their CA directory and contacts.
No parameter schema on file.
List the known ACME CA directories (Let's Encrypt production/staging...). With directory, also fetch that CA's metadata: terms-of-service URL (needed to register an account) and whether external account binding is required. Fetching directory makes the node connect to that URL, so it needs…
No parameter schema on file.
List the cluster's ACME challenge plugins (standalone HTTP and DNS API plugins). Credentials in plugin data are redacted; only their keys are shown.
No parameter schema on file.
List snapshots of every VM and container in the cluster (or a filtered set), oldest first, with guest, node, time, age in days and description. Use older_than_days to find stale snapshots that hold back storage space and slow down disks. Guests whose snapshots can't be read are reported under…
No parameter schema on file.
List API tokens (full ID user@realm!name, privilege separation, expiry, comment) for one user, or for all users when userid is omitted. Secrets can never be read back.
No parameter schema on file.
List the LXC container templates available for download from the Proxmox appliance index (Debian, Ubuntu, Alpine..., and TurnKey apps). Download one with proxmox_download_appliance_template. If the list is empty, the node may need pveam update.
No parameter schema on file.
Browse the files inside a Proxmox Backup Server backup (single-file restore): start at path "/" to see the archives (disk images/filesystem archives), then drill into directories. Only works for PBS storages. Opening VM disk images starts a temporary restore VM on the node and can take a while on…
No parameter schema on file.
List the cluster's scheduled backup (vzdump) jobs: schedule, next run, enabled, target storage, mode, which guests (all/VMID list/pool, exclusions), compression and retention. See proxmox_get_backup_job for one job with the guests and disks it covers, and proxmox_list_unbacked_guests for guests no…
No parameter schema on file.
List backup archives across every storage that holds backups (local dirs, NFS/CIFS, Proxmox Backup Server...), newest first: volume ID, guest, time, size, format, notes, protection and PBS verification state. Filter by vmid, type, storage, node or age. Shared storages are listed once. Use the…
No parameter schema on file.
List CephFS file systems with their metadata and data pools. MDS daemons serving them are listed by proxmox_list_ceph_services.
No parameter schema on file.
List Ceph OSDs from the OSD tree: host, up/down, in/out, device class, usage, PGs, CRUSH weight, latency and version, plus the per-host grouping and cluster-wide OSD flags (noout etc.). Filter by host, status or device class.
No parameter schema on file.
List Ceph pools with replication (size/min_size), PG count and autoscale mode (with the autoscaler's optimal PG count), application, CRUSH rule and usage %. Related: proxmox_get_ceph_pool, proxmox_update_ceph_pool.
No parameter schema on file.
List Ceph daemons of one type or all: monitors (quorum, rank), managers (active/standby) and metadata servers (MDS state, CephFS, rank), with host, address and version.
No parameter schema on file.
List LXC containers across the cluster with status, node, CPU, memory, disk, uptime, tags and pool. For VMs and containers together use proxmox_list_guests.
No parameter schema on file.
List cluster-wide custom CPU models (base model plus flag changes). VMs use them as cpu: custom-<name>. Related: proxmox_get_node_capabilities for built-in models and flags.
No parameter schema on file.
List the directory storages Proxmox manages on a node's disks (filesystems mounted under /mnt/pve/<name> via systemd mount units).
No parameter schema on file.
List a node's physical disks with device path, model, serial, size, type (ssd/hdd/nvme/usb), SMART health, wearout and what uses them (LVM, ZFS, Ceph OSD, partitions, mounted). Use type=unused to find disks free for new storage.
No parameter schema on file.
List IP/network aliases defined at datacenter (cluster) or guest level. Aliases are named addresses usable in rule source/dest.
No parameter schema on file.
List the datacenter's security groups (reusable rule sets) with their comment and rule count. See a group's rules with proxmox_list_firewall_rules scope=group; apply a group to a guest/node with a rule of type group.
No parameter schema on file.
List IP sets at datacenter (cluster) or guest level with their entries (CIDRs, nomatch exclusions, comments). Reference them in rules as +name (or +dc/name, +guest/name). Special sets: 'management' (hosts allowed to reach the web UI/SSH when the firewall is on), 'blacklist', and per-NIC…
No parameter schema on file.
List the predefined firewall macros (SSH, HTTP, DNS, Ceph, ...) usable as a rule's macro instead of proto/port.
No parameter schema on file.
List the aliases and IP sets that can be used in rule source/dest at datacenter (cluster) or guest level, with the exact reference string to use (e.g. +dc/management, dc/myalias).
No parameter schema on file.
List the firewall rules of the datacenter (cluster), a node, a VM/container (guest) or a security group, in evaluation order (pos 0 first). Each rule has a readable one-line form like 'IN SSH(ACCEPT) -i net0 -source +mgmt # admins'. Rules of type group pull in a security group's rules. For 'why…
No parameter schema on file.
List user groups with their members and comments.
No parameter schema on file.
List virtual machines and containers across the cluster with status, node, CPU, memory, disk, uptime, tags and pool. Filter by type, node, status, tag, pool or a search string, and sort by resource use.
No parameter schema on file.
List HA groups (node lists with priorities, restricted, nofailback). Deprecated in PVE 9, where groups are migrated to node-affinity rules (proxmox_list_ha_rules).
No parameter schema on file.
List HA-managed VMs and containers with their requested state, group, restart/relocate limits, failback, comment, guest name and current status (node and CRM state).
No parameter schema on file.
List HA rules (PVE 9+): node-affinity rules (which nodes resources prefer or must run on, with priorities) and resource-affinity rules (keep resources together or apart).
No parameter schema on file.
List a node's LVM volume groups with size, free space and physical volumes.
No parameter schema on file.
List a node's LVM thin pools with data and metadata usage. Thin pools that run out of metadata space fail badly, so watch metadata_usage.
No parameter schema on file.
List external metric servers (InfluxDB, Graphite, OpenTelemetry) that Proxmox sends performance data to.
No parameter schema on file.
List the mediated device (mdev, e.g. NVIDIA vGPU / Intel GVT-g) types a PCI device offers, with how many instances are still available. Use a device with mdev support from proxmox_list_node_pci_devices.
No parameter schema on file.
List a node's network configuration: physical NICs, Linux bridges, bonds, VLANs and OVS objects with addresses, gateways, ports and comments. Interfaces that are configured but not active are flagged; that usually means pending (unapplied) changes from proxmox_save_node_network_interface, or a…
No parameter schema on file.
List a node's PCI devices for passthrough planning: address, class, vendor/device names and IDs, IOMMU group (with the other devices in the same group, which must be passed through together) and whether it supports mediated devices (vGPU). Memory controllers, bridges and processors are hidden…
No parameter schema on file.
List a node's APT repositories by file with enabled/disabled state, URIs, suites and components, any parse errors and warnings (e.g. enterprise repo without subscription, mixed suites), and which standard Proxmox repositories are configured. Use path/index and the digest with…
No parameter schema on file.
List the Proxmox-related system services on a node (pveproxy, pvedaemon, corosync, pve-cluster, chrony, sshd, postfix...) with their running state and whether they are enabled. Failed services are listed first.
No parameter schema on file.
List the package updates available on a node (from the last package index refresh) with installed and new versions, origin and priority, plus counts. Run proxmox_refresh_node_updates first for fresh results. Installing updates is not available through the API.
No parameter schema on file.
List a node's USB devices for passthrough: vendor:product ID, manufacturer and product names, bus/port path, speed and serial. Pass a device to a VM by ID (host=vendor:product) or port (host=bus-port), or via a USB resource mapping.
No parameter schema on file.
List the cluster's nodes with online state, CPU and memory usage, uptime and subscription level.
No parameter schema on file.
List notification matchers: rules that route notifications (by severity, metadata fields such as type/hostname/job-id, and calendar time) to targets.
No parameter schema on file.
List all notification targets (endpoints of every type: sendmail, smtp, gotify, webhook) with type, disabled state, origin and comment. details=true adds each endpoint's configuration (secrets redacted). Matchers decide which notifications go to which target; see proxmox_list_notification_matchers.
No parameter schema on file.
List resource pools (groups of VMs, containers and storage used for permissions and organisation) with their comments and member counts. Not ZFS or Ceph pools; see proxmox_get_pool for members.
No parameter schema on file.
List every privilege Proxmox knows (derived from the built-in Administrator role, which holds them all), grouped by area. Use when building a custom role with proxmox_save_role.
No parameter schema on file.
List scheduled realm sync jobs (periodic LDAP/AD/OpenID user and group sync) with schedule, last and next run.
No parameter schema on file.
List authentication realms (pam, pve, LDAP, Active Directory, OpenID Connect) with type, TFA provider and comment.
No parameter schema on file.
List storage replication jobs (ZFS-based guest replication to another node) with guest, target, schedule, rate limit and live status from the source node: last/next sync, duration, failure count and last error.
No parameter schema on file.
List cluster resource mappings of one kind: PCI or USB devices, or directories (for virtiofs), each mapping a logical name to the device/path on every node. VMs reference them as e.g. hostpci0: mapping=<id>, which allows migration. With check_node, Proxmox validates the entries for that node.
No parameter schema on file.
List cluster resources of any kind from /cluster/resources: nodes, guests, storage, pools and SDN zones. Use proxmox_list_guests for a friendlier guest list.
No parameter schema on file.
List roles with their privileges. Built-in roles (Administrator, PVEAdmin, PVEVMAdmin, PVEAuditor, NoAccess...) are flagged builtin=true and cannot be changed. Use privileges=false for names only.
No parameter schema on file.
List SDN fabrics (PVE 9 underlay networks: OpenFabric, OSPF, WireGuard, BGP) with their nodes. Give node and fabric to also read that node's live fabric routes, neighbors and interfaces. Read-only; fabrics are edited in the web UI or with proxmox_api_request.
No parameter schema on file.
List Software-Defined Networking objects of one kind: zones, vnets, subnets of a vnet, controllers, IPAMs or DNS plugins. Use pending=true to see uncommitted changes (state new/changed/deleted). Related: proxmox_get_sdn_object for one object, proxmox_get_sdn_status for the live state on nodes.
No parameter schema on file.
List SDN routing policy objects (PVE 9): prefix lists with their entries, and route maps with their entries (match/set clauses). Read-only. These are referenced by controllers (route-map-in/out) and fabrics (route_filter).
No parameter schema on file.
List the snapshots of a VM or container (the type is detected from the VMID): name, parent, description, creation time, age, whether RAM state was saved (VMs), and which snapshot the guest currently runs from, plus an indented tree view. For stale snapshots across all guests use…
No parameter schema on file.
List the datacenter's storage definitions (local dirs, LVM, ZFS, NFS, CIFS, PBS, Ceph...) with type, allowed content, shared/enabled flags, node restriction, server/path/pool details and backup retention, merged with each node's live status and usage. Use proxmox_list_storage_content to see what's…
No parameter schema on file.
List the volumes on a storage: ISO images, container templates, backups, VM/CT disks, snippets and import files, with format, size, owner VMID, creation time, notes and protection. Filter by content type or VMID (e.g. all backups of guest 100).
No parameter schema on file.
List Proxmox tasks (backups, migrations, starts, clones...). Without node, lists recent tasks across the whole cluster; with node, reads that node's task history with server-side filters. Use errors=true to find failures.
No parameter schema on file.
List users' second factors (TOTP, WebAuthn, recovery keys, Yubico) with type, description, creation time and enabled state, plus TFA lock-outs. No secrets are returned. Unlock a locked-out user with proxmox_unlock_tfa.
No parameter schema on file.
List VMs and containers that no backup job covers, with node and status. Use it to audit backup coverage; add them with proxmox_save_backup_job or back them up once with proxmox_backup_guests.
No parameter schema on file.
List Proxmox users with enabled state, expiry, realm, name, email, groups, API token count and TFA lock-out state. Use proxmox_get_user for one user's details and tokens.
No parameter schema on file.
List QEMU VMs straight from the nodes (GET /nodes/{node}/qemu?full=1), with details proxmox_list_guests lacks: disk I/O counters, host memory, PSI pressure stalls and the running QEMU version/machine. Without node, queries every online node. For a quick cluster-wide list with filters by tag/pool…
No parameter schema on file.
List a node's ZFS pools (zpools) with size, allocation, fragmentation, dedup ratio and health. Use proxmox_get_zfs_pool for the vdev tree and scrub status.
No parameter schema on file.
Dry run of pruning a backup storage: shows which backups the retention rules (the storage's own, or retention) would keep and which they would remove. Nothing is deleted; run proxmox_prune_backups with the same arguments to apply.
No parameter schema on file.
Discover storage that can be added with proxmox_save_storage: NFS exports or CIFS shares on a server, PBS datastores, iSCSI targets on a portal, or local LVM volume groups, LVM thin pools and ZFS pools on a node. The nfs, cifs, pbs and iscsi scans make the node contact the given server, possibly…
No parameter schema on file.
Show the next run times of a Proxmox calendar-event schedule (as used by backup, replication and other jobs), e.g. 'mon..fri 02:00' or '*/15'. Useful to check a schedule before saving it.
No parameter schema on file.
Wait until a running task finishes (or the timeout passes) and return its outcome and log tail.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Proxmox VE or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing ships as a container image. The scanner reads packages on npm and PyPI and public source; an image is neither, so there is no grade here — not a withheld one, an unmeasured one.
Release history
It installs from a container image rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.5.1.
0.5.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Proxmox VE can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.