Manage Proxmox VE through AI assistants
Connect Runs on your machine
claude mcp add mcp-pve -e PVE_BASE_URL=<PVE_BASE_URL> -e PVE_TOKEN_ID=<PVE_TOKEN_ID> -e PVE_TOKEN_SECRET=<PVE_TOKEN_SECRET> -- npx -y @samik081/[email protected]{
"mcpServers": {
"mcp-pve": {
"command": "npx",
"args": [
"-y",
"@samik081/[email protected]"
],
"env": {
"PVE_BASE_URL": "<PVE_BASE_URL>",
"PVE_TOKEN_ID": "<PVE_TOKEN_ID>",
"PVE_TOKEN_SECRET": "<PVE_TOKEN_SECRET>"
}
}
}
}{
"mcpServers": {
"mcp-pve": {
"command": "npx",
"args": [
"-y",
"@samik081/[email protected]"
],
"env": {
"PVE_BASE_URL": "<PVE_BASE_URL>",
"PVE_TOKEN_ID": "<PVE_TOKEN_ID>",
"PVE_TOKEN_SECRET": "<PVE_TOKEN_SECRET>"
}
}
}
}{
"servers": {
"mcp-pve": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@samik081/[email protected]"
],
"env": {
"PVE_BASE_URL": "<PVE_BASE_URL>",
"PVE_TOKEN_ID": "<PVE_TOKEN_ID>",
"PVE_TOKEN_SECRET": "<PVE_TOKEN_SECRET>"
}
}
}
}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_BASE_URLRequired | URL of the Proxmox VE instance (e.g. https://pve.example.com:8006) |
PVE_TOKEN_IDRequired, secret | Proxmox VE API token ID (e.g. user@pam!token-name) |
PVE_TOKEN_SECRETRequired, secret | Proxmox VE API token secret |
Details
| Package | @samik081/[email protected] (NPM, stdio) |
| Package | ghcr.io/samik081/mcp-pve:0.11.0 (OCI, stdio) |
| First published | 12 Nov 2026 |
| Last updated | 12 Nov 2026 |
| Registry name | io.github.Samik081/mcp-pve |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.