Server providing Argo CD integration for MCP clients.
Rust Proxmoxmcp 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.
What it does
Proxmox VE MCP server for many clusters: guest protection, plan/approve/apply change control. Rust.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user rust-proxmoxmcp '--' docker run -i --rm ghcr.io/mechubsec/rustproxmoxmcp --transport stdio --state-file /var/lib/proxmoxmcp/changeset-state.json
# 2 — ask your agent for something these tools do
# get_cluster_status, get_nodes, get_node_status and 59 more
Rust Proxmoxmcp costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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 Rust Proxmoxmcp 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.
This is a public server: you run it yourself and this marketplace is not in the path. You need Docker installed and running. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user rust-proxmoxmcp '--' docker run -i --rm ghcr.io/mechubsec/rustproxmoxmcp --transport stdio --state-file /var/lib/proxmoxmcp/changeset-state.jsonReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
62 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.
Cluster quorum and node membership.
No parameter schema on file.
All nodes in the cluster with status and resource totals.
No parameter schema on file.
Detailed status for one node.
No parameter schema on file.
All HA rules (node-affinity and resource-affinity) in the cluster. Not the deprecated HA groups mechanism.
No parameter schema on file.
One HA rule by id.
No parameter schema on file.
QEMU guests across the cluster, with node, status and tags. Paginated: returns up to limit (default 500, max 700) starting at offset (default 0), plus total and has_more to page through the rest.
No parameter schema on file.
LXC guests across the cluster, with node, status and tags. Paginated: returns up to limit (default 500, max 700) starting at offset (default 0), plus total and has_more to page through the rest.
No parameter schema on file.
Configuration of one QEMU guest, including its Proxmox digest. description, cicustom and args content is redacted on a best-effort basis (do not store secrets there); sshkeys, hostname/name, resource allocation, disks…
No parameter schema on file.
Configuration of one LXC guest, including its Proxmox digest. description, cicustom and args content is redacted on a best-effort basis (do not store secrets there); sshkeys, hostname, resource allocation, disks and…
No parameter schema on file.
Network interfaces and addresses of one LXC guest.
No parameter schema on file.
Current runtime status of one guest.
No parameter schema on file.
Snapshots of one guest. description content is redacted (best-effort; do not store secrets here).
No parameter schema on file.
Storage backends visible to one node, with usage.
No parameter schema on file.
Backup archives on one storage backend. notes content is redacted (best-effort; do not store secrets here). Paginated: returns up to limit (default 500, max 700) starting at offset (default 0), plus total and has_more…
No parameter schema on file.
ISO images on one storage backend.
No parameter schema on file.
Container templates on one storage backend.
No parameter schema on file.
Recent tasks on one node. Not paginated: Proxmox's /nodes/{node}/tasks endpoint applies its own server-side default (typically the 50 most recent) and this tool does not send start/limit, so a full page here is Proxmox's…
No parameter schema on file.
Status of one task by UPID.
No parameter schema on file.
Cluster-wide firewall rules. comment content is redacted (best-effort; do not store secrets here).
No parameter schema on file.
Cluster-wide firewall options (enable flag, default in/out policy).
No parameter schema on file.
Firewall security groups defined on the cluster. comment content is redacted (best-effort; do not store secrets here).
No parameter schema on file.
Rules contained in one firewall security group. comment content is redacted (best-effort; do not store secrets here).
No parameter schema on file.
Cluster-wide IPSets. comment content is redacted (best-effort; do not store secrets here).
No parameter schema on file.
CIDR entries in one cluster-wide IPSet. comment content is redacted (best-effort; do not store secrets here).
No parameter schema on file.
Cluster-wide firewall address aliases. comment content is redacted (best-effort; do not store secrets here).
No parameter schema on file.
Firewall rules on one node. comment content is redacted (best-effort; do not store secrets here).
No parameter schema on file.
Firewall options on one node.
No parameter schema on file.
Firewall rules of one guest. comment content is redacted (best-effort; do not store secrets here).
No parameter schema on file.
Firewall options of one guest.
No parameter schema on file.
Firewall address aliases of one guest. comment content is redacted (best-effort; do not store secrets here).
No parameter schema on file.
IPSets defined on one guest. comment content is redacted (best-effort; do not store secrets here).
No parameter schema on file.
CIDR entries in one IPSet of one guest. comment content is redacted (best-effort; do not store secrets here).
No parameter schema on file.
Start a stopped QEMU guest.
No parameter schema on file.
Stop a QEMU guest immediately, without asking the guest OS.
No parameter schema on file.
Ask a QEMU guest's OS to shut down cleanly.
No parameter schema on file.
Hard power-cycle a QEMU guest.
No parameter schema on file.
Start a stopped LXC guest.
No parameter schema on file.
Stop an LXC guest immediately.
No parameter schema on file.
Reboot an LXC guest.
No parameter schema on file.
Take a snapshot of one guest. Additive, so permitted on a protected guest.
No parameter schema on file.
Back up one guest with vzdump. mode: "snapshot" (default) is additive and permitted on a protected guest; "suspend" and "stop" take the guest out of service for the duration of the backup and are refused on a protected guest…
No parameter schema on file.
Clone a guest into a new VMID. Additive, so permitted on a protected source.
No parameter schema on file.
Change an LXC guest's cores, memory or swap. Memory and swap take effect at the next start, not immediately.
No parameter schema on file.
Ask Proxmox to stop a running task. Restores and destroys are refused: stopping one half-way leaves a guest that is neither its old self nor its new one.
No parameter schema on file.
Create a QEMU guest at a free VMID. Config keys are forwarded to Proxmox as given; 'hookscript' and 'args' are refused because they execute on the node.
No parameter schema on file.
Create an LXC guest at a free VMID. Config keys are forwarded to Proxmox as given; 'hookscript' and 'args' are refused because they execute on the node.
No parameter schema on file.
Download an image to a node's storage. Requires an unrestricted guest scope, because a storage is shared and no guest selector can narrow it.
No parameter schema on file.
Grow a guest disk. Only the '+N' form is accepted. Shrinking is not supported: Proxmox itself rejects a reduction, so there is no path to it here.
No parameter schema on file.
Plan a guest destroy operation for two-principal approval.
No parameter schema on file.
Retrieve the current state of a change set.
No parameter schema on file.
Approve a planned change set as a second principal.
No parameter schema on file.
Apply an approved change set.
No parameter schema on file.
Plan an HA rule create, update or delete for two-principal approval.
No parameter schema on file.
Retrieve the current state of an HA rule change set.
No parameter schema on file.
Approve a planned HA rule change set as a second principal.
No parameter schema on file.
Apply an approved HA rule change set.
No parameter schema on file.
Plan restoring a backup archive into a new VMID, for two-principal approval.
No parameter schema on file.
Apply an approved restore-to-new-vmid change set.
No parameter schema on file.
Plan a firewall change. The firewall is not changed until the change set is approved and applied.
No parameter schema on file.
Read the state of a firewall change set, including the preview stored at plan time.
No parameter schema on file.
Approve a planned firewall change set as a second principal.
No parameter schema on file.
Apply an approved firewall change set. Refuses a change set that is not approved, or whose firewall object has changed since the plan.
No parameter schema on file.
- 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 Rust Proxmoxmcp or to call it, at any volume.
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.11.0.
No release note was published with this version.
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.
Any signed-in account that does not publish Rust Proxmoxmcp can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.