Proxmox VE MCP server

What the model can do

Proxmox VE on your own hosts: every node, VM, container and storage with status, CPU, memory, disk and uptime, cluster and quorum status, one guest's live status, the task log and one task's outcome, storage usage, backups and snapshots; when you ask, can start, shut down, reboot or stop a VM or container, suspend, resume or reset a VM, take, roll back or delete a snapshot, back up guests, and stop a running task.

Reads

• proxmox_cluster_resourcesEverything in the Proxmox cluster in one call: nodes, VMs, containers and storages with status, CPU %, memory and disk in GiB, uptime, HA state…
• proxmox_cluster_statusThe Proxmox cluster's name, whether it is quorate, and each node with online state, IP and whether it is the local one.
• proxmox_guest_statusOne Proxmox VM or container's live status: running or stopped, QEMU status, CPU %, memory, disk, network and disk I/O counters, uptime, HA…
• proxmox_list_tasksThe Proxmox task log: start, stop, backup (vzdump), migrate and other jobs with who ran them, when, and their outcome ("OK" or the error).
• proxmox_task_statusWhether one Proxmox task has finished and how: running or stopped, and its exit status ("OK" or the error).
• proxmox_storageStorage on one Proxmox node: each datastore's type, what it holds, whether it is active, enabled and shared, and used…
• proxmox_list_backupsBackups held on one Proxmox storage: volume id, guest, size, format, when it was made, whether it is protected, and verification state, newest first.
• proxmox_list_snapshotsSnapshots of one Proxmox VM or container: name, description, when taken, parent, and whether RAM state was saved.

Acts, when you ask

These change something in Proxmox VE. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• proxmox_start_guestStarts one stopped Proxmox VM or container.
• proxmox_shutdown_guestShuts down one Proxmox VM or container cleanly (an ACPI power-button press for a VM), so its users lose the service until it is started again.
• proxmox_reboot_guestReboots one Proxmox VM or container (shuts it down and starts it again, applying pending changes); its users lose the service briefly.
• proxmox_stop_guestStops one Proxmox VM or container immediately: the process is killed, like pulling the power plug, which can lose or corrupt data inside the guest.
• proxmox_suspend_vmSuspends (pauses) one running Proxmox VM in memory; it stops responding until resumed.
• proxmox_resume_vmResumes one suspended Proxmox VM.
• proxmox_reset_vmHard-resets one Proxmox VM, like pressing a reset button: the guest restarts without shutting down, which can lose unsaved data inside it.
• proxmox_create_snapshotTakes a snapshot of one Proxmox VM or container under the name given, using space on its storage.
• proxmox_rollback_snapshotRolls one Proxmox VM or container back to a snapshot, permanently discarding everything that changed since it was taken.
• proxmox_delete_snapshotDeletes one snapshot of a Proxmox VM or container, permanently.
• proxmox_backup_guestsRuns a backup (vzdump) now of the listed VMs or containers on one node, to the storage given (or the node's default).
• proxmox_stop_taskStops one running Proxmox task (a backup, migration or other job), leaving whatever it was doing unfinished.

Connect it

First connect Proxmox VE on Dashboard → Connections, then add Memtro to your client once. The Proxmox VE tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Proxmox VE connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which VMs are using the most memory right now?
• › Is the cluster quorate?
• › Did last night's backups finish OK?
• › What snapshots does VM 104 have?
• › How full is the backup storage on pve1?

Questions

Is this an official Proxmox VE MCP server?

No. It is Memtro's MCP server with Memtro's Proxmox VE connector behind it: the connector reads Proxmox VE through its API with the credentials you connect on Dashboard → Connections, and Proxmox VE publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Proxmox VE?

Only when you ask, and only what it has been granted: start a VM or container; shut down a VM or container (clean ACPI shutdown, optionally forced); reboot a VM or container; stop a VM or container immediately (like pulling the plug); suspend a VM; resume a suspended VM; reset a VM (hard reset); take a snapshot of a VM or container; roll back a VM or container to a snapshot (discards everything since); delete a snapshot; back up VMs or containers by id; stop a running task. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server