Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Proxmox VE in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
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.
Try asking
Example prompts for Proxmox VE
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Proxmox VE, paste your credentials, mint an MCP API key — done. No Docker, no
git clone, no local server.
Proxmox VE + Microsoft Copilot
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.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
PROXMOX_URL, PROXMOX_TOKEN_ID, PROXMOX_TOKEN_SECRET
Step 1 — Get credentials
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.
…(continued in the in-app connector instructions)
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
Proxmox VEtools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
proxmox_get_version | Read the Proxmox VE version and release of the connected node |
proxmox_list_cluster_resources | List every VM, container, node and storage across the whole cluster in one call, with status, CPU, memory and disk usage |
proxmox_list_nodes | List the cluster's nodes with their status, uptime, CPU count and memory |
proxmox_get_node_status | Read one node's live status: load average, CPU and memory usage, root filesystem usage, kernel version and uptime |
proxmox_list_vms | List the QEMU virtual machines on one node, with their VMID, name, status, CPU and memory allocation and current usage |
proxmox_get_vm_status | Read one virtual machine's live status: running or stopped, uptime, CPU and memory usage, disk and network throughput |
proxmox_get_vm_config | Read one virtual machine's configuration: its disks, network interfaces, boot order, CPU type and the notes recorded against it |
proxmox_list_containers | List the LXC containers on one node with their VMID, name, status and resource usage |
proxmox_list_storage | List the storage configured on one node with each store's type, total and used space, and what content it accepts |
proxmox_list_backups | List the backup archives on one storage, with their VMID, creation time, size and format — the answer to 'when was this last backed up' |
proxmox_list_tasks | List recent tasks on one node with their type, VMID, user, start time and exit status — where a failed backup or migration shows up |
FAQ
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
- Connector landing page
- Connect to Claude
- Connect to ChatGPT
- Connect to Cursor
- Connect to Gemini
- Connect to Meta Muse
Was this guide helpful?