Manage Proxmox VE through AI assistants
Set these up before or after installing:
Environment variable: PVE_BASE_URL
Environment variable: PVE_TOKEN_ID
Environment variable: PVE_TOKEN_SECRET
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-samik081-mcp-pve": {
"env": {
"PVE_BASE_URL": "your-pve-base-url-here",
"PVE_TOKEN_ID": "your-pve-token-id-here",
"PVE_TOKEN_SECRET": "your-pve-token-secret-here"
},
"args": [
"-y",
"@samik081/mcp-pve"
],
"command": "npx"
}
}
}The MCP PVE server is well-designed with proper authentication, appropriate access controls through tiered permissions, and clean code structure. While it requires broad network access and manages Proxmox VE credentials, these permissions are entirely appropriate for its stated purpose of providing AI assistants with Proxmox virtualization management capabilities. Supply chain analysis found 1 known vulnerability in dependencies (1 critical, 0 high severity). Package verification found 1 issue.
Scanned 4 files · 5 findings
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Be the first to review this server!