CyberHawk Veeam MCP

By CyberHawk Threat Intel · Rudra Verma | Senior Cyber Security Architect & Researcher

A full-operator Model Context Protocol (MCP) server for Veeam Backup & Replication — let Claude read AND control your backup infrastructure through natural language.

---

What this is

CyberHawk Veeam MCP turns Claude (Code, Desktop, or any MCP-compatible client) into a hands-on operator for Veeam Backup & Replication. Instead of only asking about your backups, you can drive them:

"Start the nightly ESXi backup job." "Why did the SQL replica job fail last night — and fix it." "Which repository is almost full?" "Show me any malware detection events from the last week." "Create a new backup job for the three web VMs, daily at 2am, to the main repository."

It speaks the VBR Public REST API v1 directly — the same documented API the Veeam console uses — so it supports full read + write across jobs, sessions, backups, restores, infrastructure, and threat detection.

How this differs from the official Veeam MCP

The official veeam-ai/veeam-mcp-server is a read-only proxy to Veeam's cloud "Veeam Intelligence" chatbot — it exposes a single question-answering tool and requires Advanced mode + a non-Community license. CyberHawk Veeam MCP is a different design: it talks straight to your VBR's on-box REST API, needs no cloud service, and exposes granular operator tools with real write capability.

	Official Veeam MCP	CyberHawk Veeam MCP
Backend	Veeam Intelligence cloud chatbot	VBR on-box REST API v1
Capability	Read-only Q&A	Full read + write operator
Tools	1 (question answering)	30+ granular tools
License requirement	Non-Community + Advanced mode	Enterprise Plus (REST API gate)
Cloud dependency	Yes	No — stays on your network

⚠️ Authorized use only. This server can start, stop, create, and delete jobs and launch restores against production backup infrastructure. Run it only against Veeam instances you own or are authorized to operate. Ships with a VEEAM_READONLY safety switch.

---

Capabilities (30+ tools)

Category	Tools
Discovery	veeam_server_info, veeam_api_request (raw escape-hatch to any endpoint)
Jobs — read	list_jobs, get_job, list_job_states, get_job_objects
Jobs — control	start_job, stop_job, retry_job, enable_job, disable_job
Jobs — config	create_job, update_job, delete_job
Sessions & diagnosis	list_sessions, get_session, get_session_logs, stop_session, diagnose_job
Backups & restore points	list_backups, get_backup_objects, list_restore_points, get_restore_point
Restore	list_restore_sessions, start_instant_recovery_vmware, stop_restore_session
Infrastructure	list_repositories, get_repository_states, list_proxies, list_managed_servers, list_credentials, browse_inventory
Security (VBR 12.1+)	list_malware_events, get_malware_settings

Not limited to hardcoded endpoints. The veeam_api_request tool can reach any VBR REST endpoint (failover plans, SureBackup, tape, agents, cloud/SaaS) — so new-version features work without waiting for a code update.

Cross-version by design. The required x-api-version header is auto-detected: the server tries your configured value, then falls back through every known VBR rev until authentication succeeds — so the same build runs against VBR 12.0, 12.1, 12.2, 12.3, and forward.

---

Requirements

• Node.js 20+ (or Docker) on the machine that runs the MCP server
• Veeam Backup & Replication 12.0 or newer with the RESTful API service running (default TCP port 9419)
• An Enterprise Plus license (or an Enterprise Plus trial / NFR key) on the VBR server — see the license note below
• A Veeam account (Windows local/domain account) that can log into the VBR console
• An MCP client: Claude Code, Claude Desktop, VS Code, etc.

⚠️ License requirement — the Veeam REST API needs Enterprise Plus. This is a Veeam licensing gate, not a limitation of this project. On Community Edition (or when no valid license is installed), the RESTful API service loads but stays in standby mode and never binds port 9419 — so nothing will answer. Veeam offers free 30-day Enterprise Plus trials and NFR keys that enable it. Verify your API is live by confirming https://<vbr-host>:9419/swagger loads.

Quick check that the listener is up (PowerShell): Test-NetConnection localhost -Port 9419. If it reports TcpTestSucceeded : False, check your license edition in Console → Help → License Information — it must be Enterprise Plus.

---

Installation

Option A — One line, no clone (recommended)

The install command is npx -y github:rudraverma/veeam-mcp — but you don't run it yourself in a terminal. With MCP, your client (Claude Desktop / Code) runs it for you every time it starts. You just tell the client to use that command by adding the block below to its config — the "command" and "args" lines are the npx command:

npx -y github:rudraverma/veeam-mcp
        └── expressed as →  "command": "npx", "args": ["-y", "github:rudraverma/veeam-mcp"]

Fastest (Claude Code) — one command that does everything

If you use Claude Code, skip editing any files — run one command and it registers the server for you:

claude mcp add veeam -s user \
  -e VEEAM_HOST=localhost \
  -e VEEAM_USERNAME=svc-claude \
  -e VEEAM_ACCEPT_SELF_SIGNED=true \
  -e VEEAM_READONLY=true \
  -- npx -y github:rudraverma/veeam-mcp

That's it. Add your Veeam password as one more -e flag (same -e VEEAM_...=value form as the others), then restart Claude Code. Flip VEEAM_READONLY to false once your first read-only connection checks out. Manage it later with claude mcp list and claude mcp remove veeam.

-s user installs it for your whole user account (every project). Drop it for a project-only install, or use -s project to share it with a repo via .mcp.json.

Any other MCP client — edit the config file

Step 1. Open your MCP client config file:

• Windows: %APPDATA%\Claude\claude_desktop_config.json
• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Step 2. Add this block (fill in your Veeam details) and save:

{
  "mcpServers": {
    "veeam": {
      "command": "npx",
      "args": ["-y", "github:rudraverma/veeam-mcp"],
      "env": {
        "VEEAM_HOST": "localhost",
        "VEEAM_PORT": "9419",
        "VEEAM_USERNAME": "DOMAIN\\svc-claude",
        "VEEAM_PASSWORD": "<your-password>",
        "VEEAM_ACCEPT_SELF_SIGNED": "true",
        "VEEAM_READONLY": "false"
      }
    }
  }
}

Step 3. Restart your MCP client. That's it — no clone, no build, no other steps.

Prefer to run the command yourself first? (Optional sanity check.) Set your VEEAM_* variables in the shell environment (or copy .env.example to .env and fill it in), then run the command below. It prints a connected to … line and then waits for the client — press Ctrl+C to exit:

npx -y github:rudraverma/veeam-mcp

Notes:

• Requires: git and Node.js 20+ on your PATH (that's all npx needs).
• First launch takes ~30–60s while npx installs and builds; every launch after that is instant from cache.
• Point VEEAM_HOST at a remote VBR IP/hostname if the MCP isn't running on the backup server itself.
• Start safe: set VEEAM_READONLY to "true" for your first connection to confirm everything reads correctly, then flip to "false" for full control.

Recommended: use a dedicated Veeam service account (e.g. svc-claude, non-MFA — Veeam's REST API and MFA don't mix) with a role assigned under Users and Roles in the console, rather than a personal admin login.

Option B — From source (offline / air-gapped / development)

Clone and build once, then launch the built file directly.

Windows (PowerShell):

git clone https://github.com/rudraverma/veeam-mcp.git
cd veeam-mcp
npm install        # runs the build automatically (prepare script)

macOS / Linux:

git clone https://github.com/rudraverma/veeam-mcp.git
cd veeam-mcp
npm install        # runs the build automatically (prepare script)

Then point your client at the built file (adjust the path):

{
  "mcpServers": {
    "veeam": {
      "command": "node",
      "args": ["/path/to/veeam-mcp/build/index.js"],
      "env": {
        "VEEAM_HOST": "localhost",
        "VEEAM_PORT": "9419",
        "VEEAM_USERNAME": "svc-claude",
        "VEEAM_PASSWORD": "your-password",
        "VEEAM_ACCEPT_SELF_SIGNED": "true",
        "VEEAM_READONLY": "false"
      }
    }
  }
}

Optional smoke test before wiring it into a client — copy .env.example to .env, fill it in, then:

npm start            # prints "connected to https://<host>:9419 …" on stderr
npm run inspector    # or click through the tools in the MCP Inspector

Option C — Docker

git clone https://github.com/rudraverma/veeam-mcp.git && cd veeam-mcp
docker build -t veeam-mcp .

{
  "mcpServers": {
    "veeam": {
      "command": "docker",
      "args": ["run", "--rm", "-i", "--env-file", "/path/to/.env", "veeam-mcp"]
    }
  }
}

Restart your MCP client after editing the config.

---

Configuration reference

Variable	Default	Description
VEEAM_HOST	localhost	VBR host or IP
VEEAM_PORT	9419	VBR REST API port
VEEAM_BASE_URL	(unset)	Full base URL override (wins over host/port)
VEEAM_USERNAME	(required)	Windows account that can log into VBR
VEEAM_PASSWORD	(required)	Password for that account
VEEAM_API_VERSION	1.1-rev1	Starting x-api-version guess (auto-detected)
VEEAM_ACCEPT_SELF_SIGNED	true	Accept VBR's self-signed TLS certificate
VEEAM_READONLY	false	true blocks all state-changing tools
VEEAM_TIMEOUT_MS	60000	HTTP request timeout

API version map (only needed if auto-detection is disabled by network policy):

VBR build	x-api-version
12.0	1.1-rev0
12.1	1.1-rev1
12.1.1 / 12.1.2	1.1-rev2
12.2	1.2-rev0
12.3	1.2-rev1

---

Usage examples

Once connected, talk to your MCP client naturally:

1. Health check — "Show me the state of all Veeam jobs — anything failed or warning?" → list_job_states
2. Start a job — "Run the 'ESXi-Nightly' backup job now." → list_jobs → start_job
3. Diagnose a failure — "Why did the 'SQL-Replica' job fail last night?" → diagnose_job (finds the latest session, reads the failed log records, explains the cause)
4. Fix and retry — "That failed because the repository was full — free space check, then retry the job." → get_repository_states → retry_job
5. Capacity review — "Which repositories are over 80% used?" → get_repository_states
6. Create a job — "Create a daily backup job for VMs web01, web02, web03 to the Main repository at 2am." → list_managed_servers → browse_inventory → list_repositories → create_job
7. Restore point lookup — "List the latest restore points for the DC01 VM." → list_restore_points
8. Instant recovery — "Instant-recover DC01 from last night's restore point to the ESXi lab host." → list_restore_points → start_instant_recovery_vmware
9. Threat hunt — "Any Veeam malware detection events this week? Summarize them for an IR ticket." → list_malware_events
10. Advanced / any endpoint — "Show me all failover plans." → veeam_api_request GET /api/v1/failoverPlans

---

Safety model

Backup infrastructure is critical, so the server is deliberate about writes:

• VEEAM_READONLY=true turns the server into a pure observability tool — every start/stop/create/delete/restore tool refuses to run and returns a clear message. Great for a first deployment or for read-only analysts.
• Every mutating tool is explicitly labelled (e.g. "destructive", "impactful") in its description so the model asks for confirmation on risky actions.
• No bulk destructive operations — deletes require a specific job ID; there is no wildcard delete.
• Credentials never leave your network — auth goes straight to your VBR host; there is no cloud dependency and secrets are read only from environment variables.

---

Project structure

veeam-mcp/
├── src/
│   ├── index.ts                 # MCP server entry point
│   ├── config.ts                # env config + validation + API-version candidates
│   ├── veeam/
│   │   └── VbrClient.ts          # OAuth2 auth, token refresh, version auto-detect, request layer
│   ├── util/
│   │   └── result.ts             # MCP tool result helpers
│   └── tools/
│       ├── index.ts              # registers all tool groups
│       ├── server.ts             # server_info + raw api_request
│       ├── jobs.ts               # list/get/control/create/update/delete jobs
│       ├── sessions.ts           # sessions + diagnose_job
│       ├── backups.ts            # backups + restore points
│       ├── restore.ts            # restore operations
│       ├── infrastructure.ts     # repositories, proxies, servers, credentials, inventory
│       └── security.ts           # malware detection (VBR 12.1+)
├── .env.example                  # configuration template (copy to .env)
├── Dockerfile                    # container build
├── esbuild.config.js             # bundler
├── package.json
├── tsconfig.json
├── LICENSE                       # Apache 2.0
└── README.md

---

Troubleshooting

Symptom	Fix
Cannot reach VBR at … (ECONNREFUSED)	Check VEEAM_HOST/VEEAM_PORT; confirm the Veeam RESTful API service is running (TCP 9419).
TLS error … self-signed	Set VEEAM_ACCEPT_SELF_SIGNED=true (default).
Authentication failed (401)	Verify VEEAM_USERNAME / VEEAM_PASSWORD; the account must be able to log into the VBR console. Note: MFA on the account can break REST auth (known Veeam issue) — use a dedicated non-MFA service account.
Every write returns "read-only mode"	You have VEEAM_READONLY=true; set it to false.
malwareDetection returns an error	That feature requires VBR 12.1+; older builds don't expose it.
A specific action isn't a dedicated tool	Use veeam_api_request with the endpoint from https://<host>:9419/swagger.

---

Related work

• MISP MCP Tool — full MISP threat-intelligence platform control via MCP
• MISP Claude Skill — MISP administration skill
• FortiOS Fabric Skill — Fortinet Security Fabric expert skill

---

Connect with CyberHawk Threat Intel

🦅 Sign up FREE → cyberhawkthreatintel.com

YouTube @cyberhawkconsultancy · YouTube @cyberhawkk · TikTok · X @cyberhawkintel · Telegram

Rudra Verma | Senior Cyber Security Architect & Researcher | CyberHawk Threat Intel
Authorized security research & penetration testing only. Unauthorized use is illegal.

#cyberhawkthreatintel  #cyberhawkconsultancy  #cyberhawkk  #cybersecurity  #ethicalhacking  #pentesting  #redteam  #threatintel  #infosec