Which integrations are available for this server?

Provides 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.

How do I use Veeam Intelligence MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Veeam Intelligence MCP Server check 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 Intelligence MCP Server

Official

by veeam-ai

Overview Schema Related Servers Score Discussions

TypeScript

Remote

Veeam Intelligence MCP Server

Unlocking Veeam Intelligence at the Operational Edge

The Veeam Intelligence MCP Server extends the power of Veeam Intelligence beyond native Veeam consoles, enabling trusted operational signals to be securely delivered where enterprise operations happen, at the edge and in real-time workflows.

By exposing Veeam Intelligence through the Model Context Protocol (MCP), organizations can merge Veeam's protection, recovery, malware, and compliance signals with data from ITSM, storage, cloud, security, and monitoring platforms in a unified operational workflow.

This project provides a Veeam Intelligence MCP server that integrates with any MCP-compatible client, such as Claude Desktop, Visual Studio Code, and others, to enhance monitoring and management for Veeam Backup & Replication, Veeam ONE, and Veeam Service Provider Console (VSPC).

Features

Veeam Intelligence MCP Server delivers cross-product, operational intelligence with these core capabilities:

Category	Capabilities
Platform & Version Intelligence	- Retrieve Veeam ONE, Veeam Backup & Replication, and VSPC versions- Detect patch/build drift- Identify outdated components
Environment Health	- Triggered alarms with filtering and ranking- Permanent notifications and active alarms- Severity, object, and repeat analysis
Threat & Malware Visibility	- Threat Center overview and widgets- Malware event listing and severity rollups- Detection source and false positive tracking
Backup Server Governance	- Backup server inventory and versions- Configuration backup enabled and encrypted status- Best practices and security posture per server
License & Consumption Intelligence	- License status, edition, and expiration- Instance, socket, and NAS capacity consumption- Top consumers and headroom analysis
Protected Workload Coverage	- VM, agent, application, NAS, and object protection status- Last protected time and job mapping- Unprotected workload detection
Job & Policy Operations	- Job and policy status across all job types- Failure trends, durations, and data movement- Performance outliers and bottlenecks
Live Job State & Triage	- Running, waiting, and chained jobs- Bottleneck and progress analysis- Stalled job detection heuristics
Session & History Analysis	- Session timelines and outcomes- Top failure reasons and noisy jobs- Success rate and SLA validation
Restore Point & RPO Coverage	- Restore point counts per object- RPO age and drift detection- Restore capability mapping
Repository Health & Capacity	- Repository inventory and online state- Capacity, utilization, and throttling- Fast clone and vPower NFS readiness
Proxy & Data Mover Capacity	- Proxy inventory and live state- Transport mode and concurrency- Encryption and fallback risks
WAN Acceleration	- WAN accelerator inventory- Stream capacity and cache sizing- High bandwidth mode coverage
Unstructured Data Protection	- NAS and file server inventory- Processing mode and proxy usage- Cache and IO control posture
Agent & Protection Group Health	- Protection group policies and schedules- Agent, driver, and plugin coverage- Offline and stale endpoint detection
Cloud & SaaS Workloads	- Public cloud policy and workload status- Platform-specific signals and failures- VB365 protected object inventory
Service Provider Operations (VSPC)	- Companies and resellers inventory- Managed server and agent visibility- Support case tracking
Operational Readiness & Notifications	- Global email and SIEM settings- Storage and capacity thresholds- Misconfiguration detection

Related MCP server: Veeam VBR v13 MCP Server

Why MCP for Veeam Intelligence?

Real-time, cross-system insight for operators and AI agents.
Single conversational interface for daily operations, planned changes, and incident response.
Secure, governed access, with no destructive or configuration-changing actions enabled by default.
Full customer control over deployment, data exposure, and integration with AI clients, including local and self-hosted LLMs.

Prerequisites

Docker or Node.js 24 installed on your system
One supported Veeam product installed with an active, non-Community license:
- Veeam Backup & Replication (vbr)
- Veeam ONE (vone)
- Veeam Service Provider Console (vspc)

Setup

1. Clone the repository

git clone https://github.com/veeam-ai/veeam-mcp-server
cd veeam-mcp-server

2. Gather credentials and connection details

Collect the following credentials and connection details. These values are passed to the MCP server as environment variables.

PRODUCT_NAME: The name of the Veeam product (vbr | vone | vspc)
WEB_URL: The base URL of your Veeam server web UI.
- Veeam Backup & Replication: https://vbr-srv.local/ (default port 443)
- Veeam ONE: https://veeamone-srv.local:1239/
- Veeam Service Provider Console: https://vspc-srv.local:1280/
ADMIN_USERNAME: The Veeam product administrator username, for example, .\administrator
ADMIN_PASSWORD: The administrator password
ACCEPT_SELF_SIGNED_CERT: Set to true if the Veeam product uses a self-signed SSL certificate, for example, ACCEPT_SELF_SIGNED_CERT=true

Paste these values directly into the MCP client, such as Visual Studio Code or Claude Desktop, so they are passed to the MCP process as environment variables.

Option 1: Run using Docker

1. Build the Docker image

Before using the Veeam Intelligence MCP server, build the Docker image:

# Option 1: Using make
make build

# Option 2: Using Docker directly
docker build -t veeam-intelligence-mcp-server .

2. Set up your MCP client

Set up your MCP client to start the MCP server using stdio transport.

docker run -i --rm \
  -e PRODUCT_NAME=vone \
  -e WEB_URL=https://vone-server.local:1239/ \
  -e ADMIN_USERNAME=.\\administrator \
  -e ADMIN_PASSWORD=password \
  -e ACCEPT_SELF_SIGNED_CERT=true \
  veeam-intelligence-mcp-server

Option 2: Using npm

Set up your MCP client to start the MCP server using stdio transport.

Store secrets in a `.env` file

In the MCP repository root, copy .env.example to .env and populate the values.
Configure your MCP client to run the server as follows:

npm start --prefix ~/path/to/mcp/server

Alternatively, pass secrets on the command line

# On Mac/Linux
PRODUCT_NAME=vone WEB_URL=https://vone-server.local:1239/ ADMIN_USERNAME=.\\administrator ADMIN_PASSWORD=password ACCEPT_SELF_SIGNED_CERT=true npm start --silent --prefix ~/path/to/mcp/server

# On Windows
set PRODUCT_NAME=vone && set WEB_URL=https://vone-server.local:1239/ && set ADMIN_USERNAME=.\\administrator && set ADMIN_PASSWORD=password && set ACCEPT_SELF_SIGNED_CERT=true && npm start --silent --prefix c:\\path\\to\\mcp\\server

Example usage with popular MCP clients

Claude Desktop

Add the Veeam Intelligence MCP server to your Claude Desktop configuration. Edit claude_desktop_config.json and add the following configuration.

For help locating the Claude Desktop MCP configuration file, see the Model Context Protocol documentation.

Using Docker

{
  "mcpServers": {
    "veeam-intelligence": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e", "PRODUCT_NAME",
        "-e", "WEB_URL",
        "-e", "ADMIN_USERNAME",
        "-e", "ADMIN_PASSWORD",
        "-e", "ACCEPT_SELF_SIGNED_CERT",
        "veeam-intelligence-mcp-server"
      ],
      "env": {
        "PRODUCT_NAME": "vone",
        "WEB_URL": "https://veeamone-srv:1239/",
        "ADMIN_USERNAME": "username",
        "ADMIN_PASSWORD": "secret",
        "ACCEPT_SELF_SIGNED_CERT": "true"
      }
    }
  }
}

Using npm

{
  "mcpServers": {
    "veeam-intelligence": {
      "command": "npm",
      "args": [
        "start",
        "--silent",
        "--prefix",
        "/path/to/mcp/server"
      ],
      "env": {
        "PRODUCT_NAME": "vone",
        "WEB_URL": "https://veeamone-srv:1239/",
        "ADMIN_USERNAME": "username",
        "ADMIN_PASSWORD": "secret",
        "ACCEPT_SELF_SIGNED_CERT": "true"
      }
    }
  }
}

Replace the placeholder values inside the env block with your own secrets.

Restart Claude Desktop to apply the changes. If Claude Desktop shows an MCP initialization error, review the MCP logs for troubleshooting.

# Follow Veeam Intelligence MCP server logs in real time (macOS)
tail -n 20 -F ~/Library/Logs/Claude/mcp-server-veeam-intelligence.log

Visual Studio Code

Refer to the Visual Studio Code documentation for how to set up MCP servers in VS Code.

Configure Veeam Intelligence MCP server in the current workspace

To use this MCP server with GitHub Copilot in VS Code, create a .vscode/mcp.json file in your workspace.

Create a .vscode directory in your workspace if it does not exist:

mkdir -p .vscode

Create a .vscode/mcp.json file with the following configuration.

Using Docker

{
  "inputs": [
    {
      "id": "product-name",
      "type": "pickString",
      "options": [
        "vbr",
        "vone",
        "vspc"
      ],
      "description": "Select a product name to connect VI MCP to"
    },
    {
      "id": "product-web-url",
      "type": "promptString",
      "description": "Product web UI URL for selected product"
    },
    {
      "id": "admin-login",
      "type": "promptString",
      "description": "Administrator login for selected product"
    },
    {
      "id": "admin-password",
      "type": "promptString",
      "description": "Administrator password for selected product"
    },
    {
      "id": "accept-self-signed-cert",
      "type": "promptString",
      "description": "Trust self-signed certificates of Veeam Server? (true/false)"
    }
  ],
  "servers": {
    "veeam-intelligence": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e", "PRODUCT_NAME",
        "-e", "WEB_URL",
        "-e", "ADMIN_USERNAME",
        "-e", "ADMIN_PASSWORD",
        "-e", "ACCEPT_SELF_SIGNED_CERT",
        "veeam-intelligence-mcp-server"
      ],
      "env": {
        "PRODUCT_NAME": "${input:product-name}",
        "WEB_URL": "${input:product-web-url}",
        "ADMIN_USERNAME": "${input:admin-login}",
        "ADMIN_PASSWORD": "${input:admin-password}",
        "ACCEPT_SELF_SIGNED_CERT": "${input:accept-self-signed-cert}"
      }
    }
  }
}

Using npm

{
  "inputs": [
    {
      "id": "product-name",
      "type": "pickString",
      "options": [
        "vbr",
        "vone",
        "vspc"
      ],
      "description": "Select a product name to connect VI MCP to"
    },
    {
      "id": "product-web-url",
      "type": "promptString",
      "description": "Product web UI URL for selected product"
    },
    {
      "id": "admin-login",
      "type": "promptString",
      "description": "Administrator login for selected product"
    },
    {
      "id": "admin-password",
      "type": "promptString",
      "description": "Administrator password for selected product"
    },
    {
      "id": "accept-self-signed-cert",
      "type": "promptString",
      "description": "Trust self-signed certificates of Veeam Server? (true/false)"
    }
  ],
  "servers": {
    "veeam-intelligence": {
      "type": "stdio",
      "command": "npm",
      "args": [
        "start",
        "--silent",
        "--prefix",
        "~/path/to/mcp/server"
      ],
      "env": {
        "PRODUCT_NAME": "${input:product-name}",
        "WEB_URL": "${input:product-web-url}",
        "ADMIN_USERNAME": "${input:admin-login}",
        "ADMIN_PASSWORD": "${input:admin-password}",
        "ACCEPT_SELF_SIGNED_CERT": "${input:accept-self-signed-cert}"
      }
    }
  }
}

Start MCP server in VS Code

Open Copilot.
At the bottom, click the tools icon and select the veeam-intelligence tool. The first time, click Update Tools under the veeam-intelligence section.
Fill in the prompted variables.
Once the MCP server is configured and selected in Copilot, it will answer requests that involve Veeam products.

Known issues

Running the Veeam Intelligence MCP server may fail if the connected Veeam Backup & Replication 13.0.1 instance uses multi-factor authentication (MFA). This issue will be addressed in upcoming releases.

This server cannot be installed

license - permissive license

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

–Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/veeam-ai/veeam-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Veeam Intelligence MCP Server

Features

Why MCP for Veeam Intelligence?

Prerequisites

Setup

1. Clone the repository

2. Gather credentials and connection details

Option 1: Run using Docker

1. Build the Docker image

2. Set up your MCP client

Option 2: Using npm

Store secrets in a .env file

Alternatively, pass secrets on the command line

Example usage with popular MCP clients

Claude Desktop

Using Docker

Using npm

Visual Studio Code

Configure Veeam Intelligence MCP server in the current workspace

Using Docker

Using npm

Start MCP server in VS Code

Known issues

Maintenance

Resources

Looking for Admin?

Latest Blog Posts

MCP directory API

Store secrets in a `.env` file