Veeam Intelligence MCP Skill
Interact with Veeam Backup & Replication (VBR) and Veeam ONE through an MCP (Model Context Protocol) server running in Docker.
Natural Language Commands
When the user asks things like:
"What backup jobs failed last night?"
"Show me backup status for all VMs"
"What's my backup repository capacity?"
"Which VMs haven't been backed up recently?"
"Check Veeam ONE alerts"
"Analyze backup performance trends"
What This Does
This skill wraps the Veeam Intelligence MCP server (running in Docker) and provides natural language access to:
Veeam Backup & Replication (VBR):
Backup job status and history
Repository capacity and health
VM backup status
Job configuration details
Failed job analysis
Veeam ONE:
Infrastructure monitoring
Performance analysis
Alert management
Capacity planning
Trend analysis
Prerequisites
Docker installed and running
Veeam Backup & Replication and/or Veeam ONE with active licenses (not Community Edition)
Veeam Intelligence enabled on your Veeam servers (required for Advanced Mode)
Admin credentials for Veeam servers
Installation
1. Obtain Veeam Intelligence MCP Server
The Veeam Intelligence MCP server is currently in beta.
To obtain access:
Contact Veeam directly or your Veeam account representative
Visit the official Veeam community forums
Check Veeam's official channels for beta program announcements
Once you have the MCP server package, build the Docker image:
cd /path/to/veeam-mcp-server
docker build -t veeam-intelligence-mcp-server .
2. Install This Skill
clawhub install veeam-mcp
Configuration
Create Credentials File
Create ~/.veeam-mcp-creds.json:
{
"vbr": {
"url": "https://veeam-server.yourdomain.com:443/",
"username": ".\\administrator",
"password": "your_secure_password"
},
"vone": {
"url": "https://veeam-one.yourdomain.com:1239/",
"username": ".\\administrator",
"password": "your_secure_password"
}
}
Important: Lock down the credentials file:
chmod 600 ~/.veeam-mcp-creds.json
Username Format
Local accounts: Use
".\\username"formatDomain accounts: Use
"DOMAIN\\username"or"[email protected]"Escape backslashes: Single backslash in JSON:
".\\"not".\\\\"
Enable Veeam Intelligence
For live data queries (Advanced Mode), enable Veeam Intelligence on your Veeam servers:
Veeam Backup & Replication:
Open Veeam B&R console
Go to Options → Veeam Intelligence Settings
Enable the AI assistant
Veeam ONE:
Open Veeam ONE console
Find Veeam Intelligence settings
Enable the feature
Without this, queries will only return documentation (Basic Mode).
Usage
Natural Language (OpenClaw)
Just ask naturally:
"What Veeam backup jobs failed yesterday?"
"Show me backup repository capacity"
"Check Veeam ONE alerts"
"Which VMs haven't been backed up this week?"
Command Line Scripts
# Query VBR
./scripts/query-veeam.sh vbr "What backup jobs ran in the last 24 hours?"
# Query Veeam ONE
./scripts/query-veeam.sh vone "Show current alerts"
# Test connections
./scripts/test-connection.sh vbr
./scripts/test-connection.sh vone
# List available MCP tools
./scripts/list-tools.sh vbr
How It Works
User Question → OpenClaw Skill → Docker MCP Server → Veeam API
↓
Veeam Intelligence
↓
JSON Response
Docker Container: MCP server runs in isolated container
STDIO Transport: Communicates via standard input/output
Credential Injection: Env vars passed securely from credentials file
Natural Language: Veeam Intelligence processes queries with AI
Troubleshooting
Connection Test Fails
# Check credentials file
cat ~/.veeam-mcp-creds.json | jq .
# Test Docker image
docker run -i --rm veeam-intelligence-mcp-server
# Manual connection test
echo '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0.0"}},"id":1}' | \
docker run -i --rm \
-e PRODUCT_NAME=vbr \
-e WEB_URL=https://your-server:443/ \
-e ADMIN_USERNAME='.\administrator' \
-e ADMIN_PASSWORD='yourpassword' \
-e ACCEPT_SELF_SIGNED_CERT=true \
veeam-intelligence-mcp-server
Basic Mode (Documentation Only)
If responses say "Basic mode is active", enable Veeam Intelligence on your servers.
Username Format Issues
Try
.\\username(local account)Try
DOMAIN\\username(domain account)Ensure single backslash in JSON
Security Notes
Credentials stored locally in
~/.veeam-mcp-creds.json(chmod 600)Docker container runs with non-root user
HTTPS connections with self-signed cert acceptance
No credentials exposed in logs or command history
MCP server communicates via stdin/stdout only
References
Veeam Intelligence MCP Server: Contact Veeam for beta access
License
This skill is provided as-is. Veeam Intelligence MCP server is licensed separately.
Need Help? Open an issue on GitHub or ask in the OpenClaw Discord.