Unitrends Backup

io.github.wyre-technologyPublished by GitHub account wyre-technologyv1.1.3Updated Oct 24, 2026

MCP server for Unitrends Backup — appliances, jobs, recovery points, restores, alerts.

Overview

AI-generated overview

Lets an assistant inspect Unitrends Backup appliances, jobs, recovery points and alerts, and queue restores.

What you can do
Exposes the Unitrends Backup API to MCP clients. Tools list appliances and protected assets, show running and historical backup jobs, browse recovery points, check restore progress, review open alarms, and report RPO compliance. One tool queues a restore, which the README marks as destructive and requiring confirmation.
When to use it
Useful when you want an assistant to answer questions about backup posture, job history or RPO compliance from Unitrends appliances or an MSP Console, or to start a restore without opening the Unitrends interface.
Requirements
Runs locally as a container over stdio (HTTP mode also available). Needs UNITRENDS_BASE_URL, UNITRENDS_USERNAME and UNITRENDS_PASSWORD; UNITRENDS_VERIFY_TLS can be set false for self-signed appliances. In gateway mode, credentials arrive as X-Unitrends-Base-URL, X-Unitrends-Username and X-Unitrends-Password headers. Network access to the appliance is required.
Before you install
The server holds Unitrends API credentials (UNITRENDS_PASSWORD) that grant access to backup infrastructure. The restore tool is described as destructive and requires confirmation. Setting UNITRENDS_VERIFY_TLS to false disables certificate verification. In gateway mode, credentials are passed in request headers.

Installation

In SourceWeft

  1. Open Unitrends Backup in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Unitrends Backup MCP Server

[CI] [License: Apache 2.0]

A Model Context Protocol server exposing the Unitrends Backup API to Claude and other MCP clients.

What it does

Surface backup posture from your Unitrends appliances (or MSP Console) directly to AI assistants — list appliances and protected assets, monitor running and historical backup jobs, browse recovery points, queue restores and replication, and review open alarms and RPO compliance.

  • Interactive Appliance Card (MCP Apps): unitrends_get_appliance renders as an interactive card in MCP Apps hosts (Claude Desktop/web); neutral by default, brandable via window.__BRAND__ injection or MCP_BRAND_* env vars; plain-JSON behavior is unchanged in other hosts

Tools

ToolPurpose
unitrends_list_appliancesList appliances under the MSP Console
unitrends_get_applianceGet a single appliance's details (renders as an interactive card in MCP Apps hosts)
unitrends_list_assetsList protected assets (require applianceId — elicits if missing)
unitrends_get_assetFetch a single asset detail
unitrends_list_running_jobsCurrently running and queued backup jobs
unitrends_list_job_historyHistorical jobs (date-range elicitation)
unitrends_list_recovery_pointsRecovery points for an asset
unitrends_queue_restoreQueue a restore (DESTRUCTIVE — requires confirmation)
unitrends_get_restore_statusCheck restore progress
unitrends_list_alertsOpen alarms
unitrends_get_success_rateRPO compliance report (date-range elicitation)

Credentials

Copy .env.example. Leave CONDUIT_S2S_SECRET empty in that file.

Local (env mode and stdio)

The stdio transport reads these variables and does not use CONDUIT_S2S_SECRET.

sh
export UNITRENDS_BASE_URL="https://unitrends.example.com"export UNITRENDS_USERNAME="..."export UNITRENDS_PASSWORD="..."export UNITRENDS_VERIFY_TLS="true"   # 'false' for self-signed appliances

HTTP service-to-service auth

CONDUIT_S2S_SECRET is required when MCP_TRANSPORT=http. If it is empty, or a known placeholder (changeme, change-me, placeholder, secret, example, your-s2s-secret, your-secret, replace-me, replace-with-a-real-secret, s2s-secret), the process logs an error and exits non-zero. It never prints the secret. Generate one with openssl rand -hex 32.

MCP_ALLOW_INSECURE_DEV=1 is the only way to start HTTP without that secret. The flag must be exactly 1. The process logs a warning, does not check X-Gateway-S2S, and listens on 127.0.0.1 only. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) is ignored in that mode and the override is logged. A known placeholder still refuses to start; unset the secret to use the bypass.

MCP_HTTP_HOST is honored when a real secret is set, including 0.0.0.0. When MCP_HTTP_HOST is unset and a secret is set, the server binds 0.0.0.0. When there is no secret, the bind address is 127.0.0.1. The container image sets MCP_HTTP_HOST=0.0.0.0.

With a real secret, every /mcp request must include X-Gateway-S2S. The value is t=<unix seconds>,v1=<hex hmac-sha256>. The MAC is HMAC-SHA256 over the ASCII string t=<unix seconds> (the same prefix that appears in the header), keyed with CONDUIT_S2S_SECRET. The timestamp must be within 300 seconds of the server clock. A missing or invalid header is 401 and is rejected before any vendor credential is read.

/health stays unauthenticated, does not read credentials, and is the container health check.

Hosted (gateway mode)

AUTH_MODE=gateway (the Compose default) requires these headers on every /mcp request. A request missing any of the required headers is 401 and does not fall back to UNITRENDS_* in the process environment.

  • X-Unitrends-Base-URL (required)
  • X-Unitrends-Username (required)
  • X-Unitrends-Password (required, secret)
  • X-Unitrends-Verify-TLS (optional, default true)
  • X-Gateway-S2S (required when CONDUIT_S2S_SECRET is set)
typescript
// Gateway injects vendor credentials and the X-Gateway-S2S proofconst response = await fetch("http://gateway:8080/mcp", {  method: "POST",  headers: {    "content-type": "application/json",    accept: "application/json, text/event-stream",    "x-gateway-s2s": "<t=unix,v1=hmac-sha256 of t=unix, keyed with CONDUIT_S2S_SECRET>",    "x-unitrends-base-url": "https://unitrends.example.com",    "x-unitrends-username": "your_username",    "x-unitrends-password": "your_password",  },  body: JSON.stringify({ jsonrpc: "2.0", id: 1, method: "tools/list" }),});

Single-tenant HTTP (AUTH_MODE=env, the image default) still requires a valid X-Gateway-S2S header, then reads UNITRENDS_* from the environment when the request does not carry credential headers.

Run

sh
npm installnpm run buildnpm start                       # stdio
# HTTP refuses to start until CONDUIT_S2S_SECRET is a real secretCONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" MCP_TRANSPORT=http npm start
# Local HTTP only, without a service-to-service secret (always binds 127.0.0.1)MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm start

Docker

The image listens on 0.0.0.0 inside the container and defaults to AUTH_MODE=env. Publish the port on loopback and pass the S2S secret. HTTP will not start when CONDUIT_S2S_SECRET is empty or a known placeholder.

sh
docker build -t unitrends-mcp .docker run \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -e UNITRENDS_BASE_URL="https://unitrends.example.com" \  -e UNITRENDS_USERNAME="..." \  -e UNITRENDS_PASSWORD="..." \  -p 127.0.0.1:8080:8080 \  unitrends-mcp

Gateway mode does not read those vendor variables. Credentials arrive on each request, and the request must also carry X-Gateway-S2S signed with CONDUIT_S2S_SECRET:

sh
docker run \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -e AUTH_MODE=gateway \  -p 127.0.0.1:8080:8080 \  unitrends-mcp

Compose refuses to start when CONDUIT_S2S_SECRET is unset or empty, sets AUTH_MODE=gateway, does not inject UNITRENDS_BASE_URL, UNITRENDS_USERNAME, or UNITRENDS_PASSWORD, and publishes 127.0.0.1:8080:8080:

sh
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up

License

Apache 2.0 — see LICENSE.

Source: README.md at commit ae00585

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts