Morning health check
Tom Reilly, infrastructure lead at Northwind, asked whether anything had failed overnight. Memtro read the task log and listed the backup jobs with their outcomes, naming the one that ended with an error.
Which VMs are struggling, and did last night's backups finish?
Proxmox VE shows you every node, VM, container and storage on your own hosts, with status, CPU, memory, disk and uptime. It reads cluster and quorum status, one guest's live status, the task log, storage usage, backups and snapshots. When asked and granted, it can start, shut down, reboot or stop a VM or container, and suspend, resume or reset a VM. It can also take, roll back or delete a snapshot, back up guests, and stop a running task. With Privilege Separation ticked, the token has no rights until you add an API Token Permission for it.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Proxmox VE tool, reads what it needs, and answers with the source cited.
These tools change something in Proxmox VE. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Proxmox VE is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
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?
Tom Reilly, infrastructure lead at Northwind, asked whether anything had failed overnight. Memtro read the task log and listed the backup jobs with their outcomes, naming the one that ended with an error.
Dan Fletcher, sysadmin at Acme Ltd, asked Memtro to snapshot the database VM before patching it. With the action granted, Memtro took the snapshot and then checked the task status, which came back OK.
The teams that lean on Proxmox VE most, a question each of them asks, and what they connect beside it.
A record in Proxmox VE is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Proxmox open Datacenter, then Permissions, then API Tokens, and add a token. Give it PVEAuditor on / for reads, plus the privileges each action needs. The secret is shown once.
In Memtro open Connections → Proxmox VE. Fill in Host with the DNS name alone, Token ID exactly as Proxmox shows it, and Token secret.
Set Port only if the API is not on 8006. An administrator grants the power, snapshot and backup actions by name to the teams that may use them.
Ask: which VMs are using the most memory right now?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Proxmox VE tools are the same everywhere.
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. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Host, token ID and token secret. In Proxmox open Datacenter, then Permissions, then API Tokens, and add a token. Give it PVEAuditor on / for reads, plus the privileges each action needs. The secret is shown once.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time