Proxmox VE
Proxmox Virtual Environment: cluster nodes, virtual machines and containers with their status and resource usage, storage, backup tasks and the task log. REST API with an API token, read-only by construction.
7 天免费 · 无需信用卡 · EU 托管
问 Proxmox 任何事
通过 AnythingMCP 对 Proxmox VE 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 ProxmoxClaude 是 AI,可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Proxmox VE。提示时粘贴凭据。
- 3生成 MCP API 密钥,将 AI 客户端指向生成的 MCP URL。
配置 Proxmox VE
直接来自连接器定义:在哪里获取凭据、需要哪些权限,以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
Use an API token, not a password.
- In the Proxmox web UI go to Datacenter → Permissions → API Tokens and add a token for a user — e.g.
readonly@pvewith token idamcp. Proxmox shows the secret once. - Leave Privilege Separation ticked and grant the token the
PVEAuditorrole at path/. PVEAuditor is read-everything, change-nothing, which is exactly what this adapter needs and all it can do. - Set
PROXMOX_URLtohttps://your-host:8006,PROXMOX_TOKEN_IDto the fulluser@realm!tokenidstring, andPROXMOX_TOKEN_SECRETto the secret.
The Authorization header is PVEAPIToken=user@realm!tokenid=secret — Proxmox's own scheme, with the whole triple in one header value. The adapter assembles it; a space in the wrong place is the usual cause of a 401.
Valid TLS is required, and a fresh Proxmox does not have it. Proxmox ships a self-signed certificate on port 8006, and this connector will refuse it — there is no trust-anything switch. Put a real certificate on the host (Proxmox has built-in ACME support under Node → Certificates) or put it behind a reverse proxy that has one.
Node names scope almost everything. /nodes/{node}/qemu lists the VMs on one node. proxmox_list_cluster_resources is the exception and the better starting point: it returns every VM, container and storage across the whole cluster in one call.
VM vs container. qemu is a full virtual machine, lxc is a container. They are separate collections with the same shape, and a question about 'all the machines' needs both — or proxmox_list_cluster_resources, which covers both.
Read-only by design: no start, no stop, no snapshot, no delete. Restarting production from a chat window should be a decision, not an autocomplete.
Self-hosted, which is the thing to plan for.
- On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch, and a homelab's default certificate is exactly the case that breaks.
- On an internal host (
pve.intern,10.0.0.x), self-host AnythingMCP on the same network and add that host toSSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.