Datto BCDR

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

MCP server for Datto BCDR — appliances, agents, recovery points, screenshots, alerts.

VerifiedSTDIODesktop onlyCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Read-only MCP server for the Datto BCDR backup portal, letting an assistant inspect appliances, protected agents, recovery points, screenshots and alerts.

What you can do
  • List and inspect SIRIS/Alto appliances and their details by serial number
  • List protected agents on an appliance and fetch a single agent
  • List recovery points and screenshot verifications for an agent, and fetch a screenshot image
  • Check off-site sync status for an appliance
  • List portal alerts and activity log entries filtered by date range
  • Prompt for missing filters such as date range or serial number
When to use it
Useful for managed service providers or backup administrators who want to ask an assistant about Datto BCDR backup health: which appliances exist, whether agents are protected, when the last recovery points were taken, whether off-site sync is current, and which alerts are open.
Requirements
Runs as a local stdio process (Docker image or npm build). Requires Datto BCDR partner portal API credentials in DATTO_BCDR_PUBLIC_KEY and DATTO_BCDR_PRIVATE_KEY, plus optional DATTO_BCDR_REGION (us or eu). HTTP mode additionally requires CONDUIT_S2S_SECRET and the X-Gateway-S2S header; gateway mode takes credentials from X-Datto-BCDR-Public-Key and X-Datto-BCDR-Private-Key headers.
Before you install
Requires a partner portal public and private API key pair, which grant access to backup portal data; keep them out of logs and repositories. HTTP deployments need CONDUIT_S2S_SECRET, and the insecure development bypass should only be used locally on loopback. The listed tools read data only, but screenshots and appliance details are pulled from a third-party vendor API.

Installation

In SourceWeft

  1. Open Datto BCDR 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

Datto BCDR MCP Server

[Release] [License: Apache 2.0]

Model Context Protocol (MCP) server for the Datto BCDR (Backup Portal) API. Exposes SIRIS / Alto appliances, protected agents, recovery points, screenshot verifications, off-site sync status, alerts, and activity logs to AI assistants.

Tools

ToolDescription
datto_bcdr_list_devicesList all SIRIS/Alto appliances in the partner portal
datto_bcdr_get_deviceGet appliance details by serialNumber (renders as an interactive card in MCP Apps hosts)
datto_bcdr_list_assetsList protected agents on an appliance
datto_bcdr_get_assetGet a specific protected agent
datto_bcdr_list_backupsList recovery points for an agent
datto_bcdr_list_screenshotsList screenshot verifications for an agent
datto_bcdr_get_screenshotFetch a screenshot PNG (returned as base64 image content)
datto_bcdr_get_offsite_statusOff-site sync status for an appliance
datto_bcdr_list_alertsPortal alerts (date-range filtered)
datto_bcdr_list_activityActivity log (date-range filtered)

When the user omits required filters (date range, serial number, etc.) the server uses MCP elicitation to prompt for them.

Features

  • Interactive Device Card (MCP Apps, SEP-1865): datto_bcdr_get_device renders as a read-only interactive card in MCP Apps hosts (Claude Desktop/web) showing the appliance's backup status at a glance — neutral by default, brandable via window.__BRAND__ injection or MCP_BRAND_* env vars; plain-JSON behavior is unchanged in other hosts. Edit ui/ and run npm run build:ui to regenerate the embedded card bundle.

Configuration

Copy .env.example and set the variables below. The stdio transport reads DATTO_BCDR_* and is not affected by HTTP service-to-service auth.

VariableRequiredDescription
DATTO_BCDR_PUBLIC_KEYFor stdio and AUTH_MODE=envDatto BCDR partner portal public key
DATTO_BCDR_PRIVATE_KEYFor stdio and AUTH_MODE=envDatto BCDR partner portal private key (secret)
DATTO_BCDR_REGIONNous (default) or eu
MCP_TRANSPORTNostdio (default) or http
AUTH_MODENogateway (Docker image and Compose default) or env. Gateway mode requires X-Datto-BCDR-Public-Key and X-Datto-BCDR-Private-Key on each /mcp request and never falls back to DATTO_BCDR_*. env uses those variables only after S2S auth succeeds.
CONDUIT_S2S_SECRETYes for HTTPService-to-service secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder (replace-with-a-real-secret, your-s2s-secret, your-secret, changeme, change-me, placeholder, secret, example, replace-me, s2s-secret). Compose will not start without it. Never commit a real value. Generate one with openssl rand -hex 32. The value is never logged.
MCP_ALLOW_INSECURE_DEVNoSet to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning and does not enforce X-Gateway-S2S. The listener is forced to 127.0.0.1. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) refuses to start. A known placeholder secret still refuses to start.
MCP_HTTP_HOSTNoBind address when MCP_TRANSPORT=http. Defaults to 127.0.0.1. A configured CONDUIT_S2S_SECRET honors this value. The container image sets 0.0.0.0.
MCP_HTTP_PORTNoHTTP port. Defaults to 8080.

/health stays unauthenticated and does not read credentials.

HTTP authentication

With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. A missing or invalid header returns 401 before vendor credentials are read.

The header value is t=<unix seconds>,v1=<hex hmac-sha256>. The signed message is the ASCII string t=<unix seconds> (the same timestamp prefix), and the HMAC key is CONDUIT_S2S_SECRET. Timestamps more than 300 seconds from the server clock are rejected.

js
import { createHmac } from "node:crypto";
const t = Math.floor(Date.now() / 1000);const v1 = createHmac("sha256", process.env.CONDUIT_S2S_SECRET).update(`t=${t}`).digest("hex");const xGatewayS2s = `t=${t},v1=${v1}`;

In AUTH_MODE=gateway, /mcp also requires X-Datto-BCDR-Public-Key and X-Datto-BCDR-Private-Key (X-Datto-BCDR-Region is optional). Those headers are the only credential source for that request. A request missing either key returns 401 and does not fall back to DATTO_BCDR_PUBLIC_KEY / DATTO_BCDR_PRIVATE_KEY. Each request creates a fresh server instance with isolated credentials.

The WYRE MCP Gateway signs X-Gateway-S2S with the per-vendor subkey provisioned as CONDUIT_S2S_SECRET and injects the Datto headers:

js
await fetch("http://gateway:8080/mcp", {  method: "POST",  headers: {    "content-type": "application/json",    accept: "application/json, text/event-stream",    "x-gateway-s2s": xGatewayS2s,    "x-datto-bcdr-public-key": publicKey,    "x-datto-bcdr-private-key": privateKey,  },  body: JSON.stringify({ jsonrpc: "2.0", id: 1, method: "tools/list" }),});

Local development

bash
npm installnpm run buildDATTO_BCDR_PUBLIC_KEY=... DATTO_BCDR_PRIVATE_KEY=... npm start

HTTP refuses to start until CONDUIT_S2S_SECRET is set:

bash
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" MCP_TRANSPORT=http npm startcurl http://127.0.0.1:8080/health

Local HTTP without a service-to-service secret is development-only. It binds 127.0.0.1 only and logs a warning. A non-loopback MCP_HTTP_HOST makes startup exit. The container image sets MCP_HTTP_HOST=0.0.0.0, so this bypass also needs -e MCP_HTTP_HOST=127.0.0.1 when using the image:

bash
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm start

Docker

The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode, Datto credentials arrive on each request as headers; they are not read from the environment.

bash
docker build -t datto-bcdr-mcp .docker run --rm \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -p 127.0.0.1:8080:8080 \  datto-bcdr-mcp

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

bash
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up

Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses DATTO_BCDR_PUBLIC_KEY and DATTO_BCDR_PRIVATE_KEY:

bash
docker run --rm \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -e AUTH_MODE=env \  -e DATTO_BCDR_PUBLIC_KEY=your-value \  -e DATTO_BCDR_PRIVATE_KEY=your-value \  -p 127.0.0.1:8080:8080 \  datto-bcdr-mcp

License

Apache-2.0

Source: README.md at commit c0e0580

Tools

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

Version history

1
  1. v1.1.4LatestSep 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