Proxmox VE MCP Server
An open-source MCP server that allows AI assistants to manage Proxmox VE infrastructure. It provides 122 tools across 12 categories to handle virtual machines, containers, storage, networking, and clusters via natural language. It supports granular access tiers, category filtering, and runs via npx or Docker with native fetch.
Package and access
Local package with source-attributed installation metadata. Koskamo does not execute packages during review.
Checks and signals
Each line is separate evidence, not a trust score.
- Popularity 27 GitHub stars
What you can do with it
- Manage virtual machines and containers
- Configure storage and networking
- Administer Proxmox VE clusters
- Monitor infrastructure via AI assistants
Source and maintenance
- Last repository push
- Latest release
- v0.9.0
- Maintenance checked
Packages and installation
Source-provided package data. Koskamo has not executed or live-probed this package.
ghcr.io/samik081/mcp-pve:0.9.0
{
"transport": "stdio",
"identifier": "ghcr.io/samik081/mcp-pve:0.9.0",
"registryType": "oci",
"environmentVariables": [
{
"name": "PVE_BASE_URL",
"isRequired": true,
"description": "URL of the Proxmox VE instance (e.g. https://pve.example.com:8006)"
},
{
"name": "PVE_TOKEN_ID",
"isRequired": true,
"description": "Proxmox VE API token ID (e.g. user@pam!token-name)"
},
{
"name": "PVE_TOKEN_SECRET",
"isRequired": true,
"description": "Proxmox VE API token secret"
}
]
}Tools
Reported by the attributed source; not independently observed by Koskamo.
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · repository · passed · metadata changed · updated
- · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown
Connect from your client
Each snippet configures the same source-provided package; replace placeholders before use.
Cursor
{
"mcpServers": {
"proxmox-ve-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PVE_BASE_URL=<YOUR_PVE_BASE_URL>",
"-e",
"PVE_TOKEN_ID=<YOUR_PVE_TOKEN_ID>",
"-e",
"PVE_TOKEN_SECRET=<YOUR_PVE_TOKEN_SECRET>",
"ghcr.io/samik081/mcp-pve:0.9.0"
],
"env": {
"PVE_BASE_URL": "<YOUR_PVE_BASE_URL>",
"PVE_TOKEN_ID": "<YOUR_PVE_TOKEN_ID>",
"PVE_TOKEN_SECRET": "<YOUR_PVE_TOKEN_SECRET>"
}
}
}
}Cline
{
"mcpServers": {
"proxmox-ve-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PVE_BASE_URL=<YOUR_PVE_BASE_URL>",
"-e",
"PVE_TOKEN_ID=<YOUR_PVE_TOKEN_ID>",
"-e",
"PVE_TOKEN_SECRET=<YOUR_PVE_TOKEN_SECRET>",
"ghcr.io/samik081/mcp-pve:0.9.0"
],
"env": {
"PVE_BASE_URL": "<YOUR_PVE_BASE_URL>",
"PVE_TOKEN_ID": "<YOUR_PVE_TOKEN_ID>",
"PVE_TOKEN_SECRET": "<YOUR_PVE_TOKEN_SECRET>"
}
}
}
}VS Code
{
"servers": {
"proxmox-ve-mcp-server": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PVE_BASE_URL=<YOUR_PVE_BASE_URL>",
"-e",
"PVE_TOKEN_ID=<YOUR_PVE_TOKEN_ID>",
"-e",
"PVE_TOKEN_SECRET=<YOUR_PVE_TOKEN_SECRET>",
"ghcr.io/samik081/mcp-pve:0.9.0"
],
"env": {
"PVE_BASE_URL": "<YOUR_PVE_BASE_URL>",
"PVE_TOKEN_ID": "<YOUR_PVE_TOKEN_ID>",
"PVE_TOKEN_SECRET": "<YOUR_PVE_TOKEN_SECRET>"
}
}
}
}Claude Desktop
{
"mcpServers": {
"proxmox-ve-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"PVE_BASE_URL=<YOUR_PVE_BASE_URL>",
"-e",
"PVE_TOKEN_ID=<YOUR_PVE_TOKEN_ID>",
"-e",
"PVE_TOKEN_SECRET=<YOUR_PVE_TOKEN_SECRET>",
"ghcr.io/samik081/mcp-pve:0.9.0"
],
"env": {
"PVE_BASE_URL": "<YOUR_PVE_BASE_URL>",
"PVE_TOKEN_ID": "<YOUR_PVE_TOKEN_ID>",
"PVE_TOKEN_SECRET": "<YOUR_PVE_TOKEN_SECRET>"
}
}
}
}Let your agent find its tools
Find servers like Proxmox VE MCP Server from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.