Tractorbeeam MCP Server

MCP server for Veeam Backup for Microsoft 365: read-only review + gated, audited restore tier. Exposed over MCP by the tractorbeeam mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A Model Context Protocol server for Veeam Backup for Microsoft 365 (VB365). It talks directly to the VB365 REST API so an MCP client (Claude Code / Claude Desktop) can review your backup configuration, find protection gaps, spot trends, verify cloud immutability — and, when you explicitly opt in, run jobs and orchestrate restores.

Its toolset

Everything the assistant can do here goes through one of these:

• vb365_health_summary — One-shot review: orgs, jobs + last status, repos, cloud storage (B2/S3/Azure), proxies, license, trend anomalies, and a flags list. **Start
• vb365_trends — Per-job success/failure drift, repo capacity-full projection, restore-test cadence per org, RPO compliance
• cloud_lock_audit — Cross-checks Object Lock mode/retention/versioning at the bucket vs what VB365 reports (needs B2_/S3_)
• vb365_api_root — Resource list + version (confirms connectivity)
• vb365_list_job_sessions — Recent run results (optionally per job)
• vb365_get — Read-only GET to any other //... resource

Configuration

You will need 3 environment variables: VB365_HOST, MCP_AUTH_TOKEN, DOCKERHUB_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Tractorbeeam's toolset — vb365_health_summary, vb365_trends, cloud_lock_audit and 3 more — is a fair guide to whether it matches your workflow. It is maintained by Ringosystems; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the tractorbeeam mcp server does with a few real requests.