io.github.wyre-technology/datto-bcdr-mcp

Official

by wyre-technology · JavaScript

Datto BCDR

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

Manage Datto BCDR backup and disaster recovery appliances, agents, recovery points, and alerts.

Topics

backupbcdrclaudedattokaseyamcpmodel-context-protocolmsp

README.md3 KBView on GitHub

Datto BCDR MCP Server

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

Tool	Description
`datto_bcdr_list_devices`	List all SIRIS/Alto appliances in the partner portal
`datto_bcdr_get_device`	Get appliance details by `serialNumber`
`datto_bcdr_list_assets`	List protected agents on an appliance
`datto_bcdr_get_asset`	Get a specific protected agent
`datto_bcdr_list_backups`	List recovery points for an agent
`datto_bcdr_list_screenshots`	List screenshot verifications for an agent
`datto_bcdr_get_screenshot`	Fetch a screenshot PNG (returned as base64 image content)
`datto_bcdr_get_offsite_status`	Off-site sync status for an appliance
`datto_bcdr_list_alerts`	Portal alerts (date-range filtered)
`datto_bcdr_list_activity`	Activity log (date-range filtered)

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

Configuration

Environment-variable mode (default)

Variable	Required	Description
`DATTO_BCDR_PUBLIC_KEY`	yes	Datto BCDR partner portal public key
`DATTO_BCDR_PRIVATE_KEY`	yes	Datto BCDR partner portal private key (secret)
`DATTO_BCDR_REGION`	no	`us` (default) or `eu`
`MCP_TRANSPORT`	no	`stdio` (default) or `http`
`MCP_HTTP_PORT`	no	HTTP listen port (default `8080`)
`AUTH_MODE`	no	`env` (default) or `gateway`

Gateway mode

When deployed behind the WYRE MCP Gateway, set AUTH_MODE=gateway and the server will read credentials from per-request HTTP headers:

X-Datto-BCDR-Public-Key
X-Datto-BCDR-Private-Key
X-Datto-BCDR-Region (optional)

Each request creates a fresh server instance with isolated credentials — no cross-tenant process.env pollution.

Local development

bash

npm install
npm run build
DATTO_BCDR_PUBLIC_KEY=... DATTO_BCDR_PRIVATE_KEY=... npm start

Run as HTTP for testing:

bash

MCP_TRANSPORT=http npm start
curl http://localhost:8080/health

Docker

bash

docker build -t datto-bcdr-mcp .
docker run --rm -p 8080:8080 \
  -e DATTO_BCDR_PUBLIC_KEY=... \
  -e DATTO_BCDR_PRIVATE_KEY=... \
  datto-bcdr-mcp

License

Apache-2.0

Install

Configuration

Environment variables

DATTO_BCDR_PUBLIC_KEYrequiredsecret

Datto BCDR partner portal public API key

DATTO_BCDR_PRIVATE_KEYrequiredsecret

Datto BCDR partner portal private API key

DATTO_BCDR_REGIONdefault us

Region: 'us' (default) or 'eu'

MCP_TRANSPORTdefault stdio

Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.

AUTH_MODEdefault env

Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.

LOG_LEVELdefault info

Log verbosity: debug, info, warn, error

claude_desktop_config.json

{
  "mcpServers": {
    "datto-bcdr-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-technology/datto-bcdr-mcp:v1.0.8"
      ],
      "env": {
        "DATTO_BCDR_PUBLIC_KEY": "<YOUR_DATTO_BCDR_PUBLIC_KEY>",
        "DATTO_BCDR_PRIVATE_KEY": "<YOUR_DATTO_BCDR_PRIVATE_KEY>",
        "DATTO_BCDR_REGION": "us",
        "MCP_TRANSPORT": "stdio",
        "AUTH_MODE": "env",
        "LOG_LEVEL": "info"
      }
    }
  }
}