Veeam Aiops MCP server
{
"mcpServers": {
"aiops-tools-veeam-aiops": {
"command": "uvx",
"args": [
"veeam-aiops"
],
"env": {
"VEEAM_AIOPS_MASTER_PASSWORD": "<veeam_aiops_master_password>"
}
}
}
}{
"mcpServers": {
"aiops-tools-veeam-aiops": {
"command": "uvx",
"args": [
"veeam-aiops"
],
"env": {
"VEEAM_AIOPS_MASTER_PASSWORD": "<veeam_aiops_master_password>"
}
}
}
}{
"mcpServers": {
"aiops-tools-veeam-aiops": {
"command": "uvx",
"args": [
"veeam-aiops"
],
"env": {
"VEEAM_AIOPS_MASTER_PASSWORD": "<veeam_aiops_master_password>"
}
}
}
}{
"servers": {
"aiops-tools-veeam-aiops": {
"command": "uvx",
"args": [
"veeam-aiops"
],
"env": {
"VEEAM_AIOPS_MASTER_PASSWORD": "${input:veeam_aiops_master_password}"
}
}
},
"inputs": [
{
"id": "veeam_aiops_master_password",
"type": "promptString",
"description": "Veeam aiops master password",
"password": true
}
]
}{
"mcpServers": {
"aiops-tools-veeam-aiops": {
"command": "uvx",
"args": [
"veeam-aiops"
],
"env": {
"VEEAM_AIOPS_MASTER_PASSWORD": "<veeam_aiops_master_password>"
}
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall uvx veeam-aiopsversion 0.11.0
What it does
Veeam AIops exposes 25 MCP tools for Veeam Backup & Replication operations—job management, restore, repository monitoring, and diagnostics—wrapped in a governance harness that logs all calls to an audit database, tracks reversibility, enforces budget limits, and encrypts stored credentials. It is for developers integrating AI agents with Veeam backup infrastructure who need operational transparency and safety guardrails.
- Start, stop, enable, disable, or retry Veeam backup jobs and monitor their session progress through audit trails.
- Initiate VM restores from recovery points and diagnose backup failures by root cause (repository full, connectivity, credential issues, retry exhaustion).
- Monitor repository capacity and free space, manage encrypted credentials for multiple Veeam targets, and review all operations in the audit log.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.