Veeam Intelligence MCP Server
OfficialProvides operational intelligence for Veeam Backup & Replication, Veeam ONE, and Veeam Service Provider Console, enabling monitoring of environment health, threat visibility, backup server governance, license consumption, protected workload coverage, job operations, restore point RPO, repository health, proxy capacity, and more.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Veeam Intelligence MCP Servercheck for any failed backup jobs in the last 24 hours"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Veeam MCP Servers
This repository hosts Model Context Protocol (MCP) servers for Veeam products. Each server is an independent project with its own toolchain, dependencies, and documentation, and integrates with any MCP-compatible client, such as Claude Desktop, Visual Studio Code, and others.
Servers
Server | Directory | Stack | Description |
| TypeScript, Node.js 24 | Brings Veeam Intelligence to MCP clients for monitoring and management of Veeam Backup & Replication, Veeam ONE, and Veeam Service Provider Console (VSPC). | |
| Python 3.13, uv | Exposes the Veeam Backup & Replication REST API as MCP tools grouped by resource: jobs, sessions, backups, restore, backup infrastructure, licensing, and more. Some tools change state or can overwrite data, so read its safety section first. |
See the README of each server for prerequisites, setup, and client configuration.
Related MCP server: Veeam Backup & Replication MCP Server
Repository layout
servers/
├── vi-mcp/ # Veeam Intelligence MCP Server
└── vbr-mcp/ # Veeam Backup & Replication MCP Server
.github/ # CI workflows
LICENSEUpgrading from the previous layout
The Veeam Intelligence MCP Server moved from the repository root to servers/vi-mcp. If you set it up before this change:
npm: point
--prefixin your MCP client configuration to<repository>/servers/vi-mcpinstead of the repository root..envfile: move it from the repository root toservers/vi-mcp/.env. The old location is silently ignored.Docker: rebuild the image from
servers/vi-mcp(make buildordocker build -t veeam-intelligence-mcp-server .in that directory). The image name is unchanged, so existing MCP client configurations keep working.Remove the leftover
node_modules/andbuild/directories from the repository root.
License
This project is licensed under the MIT License. See LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Let AI agents query data and act across all your business apps via MCP.
An AI concierge that turns static forms into adaptive AI conversations. From any MCP client.
MCP-Native LLM Orchestration Agent
- ZapierOAuthcom.zapier
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
Related MCP Servers
AlicenseNot gradedqualityBmaintenanceMCP server for interacting with Keepit backup and data protection services. Enables monitoring, management, and security operations through natural language.5MIT- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Veeam Backup & Replication infrastructure through natural language, allowing monitoring, management, and troubleshooting of backup jobs, sessions, and restore points.MIT
- AlicenseAqualityAmaintenanceAI-powered Veeam Backup & Replication operations MCP server with tools for managing jobs, restores, sessions, and repositories, featuring built-in governance, audit logging, and safety controls.27MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural language interaction with VMware SDDC Manager and vCenter APIs through MCP tools, allowing users to query workload domains, VMs, clusters, and more.MIT