Proxmox VE in Claude: VMs, storage, backups; start, stop, snapshot after a yes.
Connect Runs on your machine
claude mcp add proxmox-mcp -e PVE_URL=<PVE_URL> -e PVE_TOKEN_ID=<PVE_TOKEN_ID> -e PVE_TOKEN_SECRET=<PVE_TOKEN_SECRET> -e PVE_SAMPLE=<PVE_SAMPLE> -- uvx mojood-proxmox-mcp==0.1.0
{
"mcpServers": {
"proxmox-mcp": {
"command": "uvx",
"args": [
"mojood-proxmox-mcp==0.1.0"
],
"env": {
"PVE_URL": "<PVE_URL>",
"PVE_TOKEN_ID": "<PVE_TOKEN_ID>",
"PVE_TOKEN_SECRET": "<PVE_TOKEN_SECRET>",
"PVE_SAMPLE": "<PVE_SAMPLE>"
}
}
}
}
{
"mcpServers": {
"proxmox-mcp": {
"command": "uvx",
"args": [
"mojood-proxmox-mcp==0.1.0"
],
"env": {
"PVE_URL": "<PVE_URL>",
"PVE_TOKEN_ID": "<PVE_TOKEN_ID>",
"PVE_TOKEN_SECRET": "<PVE_TOKEN_SECRET>",
"PVE_SAMPLE": "<PVE_SAMPLE>"
}
}
}
}
{
"servers": {
"proxmox-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"mojood-proxmox-mcp==0.1.0"
],
"env": {
"PVE_URL": "<PVE_URL>",
"PVE_TOKEN_ID": "<PVE_TOKEN_ID>",
"PVE_TOKEN_SECRET": "<PVE_TOKEN_SECRET>",
"PVE_SAMPLE": "<PVE_SAMPLE>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
PVE_URLRequired | Your Proxmox VE API address |
PVE_TOKEN_IDRequired | API token id (user@realm!name) |
PVE_TOKEN_SECRETRequired, secret | API token secret |
PVE_SAMPLEOptional | 0 for real data (1 labels answers SAMPLE) |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 2 Nov 2026 |
| Last updated | 2 Nov 2026 |
| Registry name | io.github.askmojood/proxmox-mcp |
More files and documents servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
