Datto BCDR MCP Server

An MCP server for the BCDR part of the Datto partner REST API (SIRIS and ALTO backup appliances). It lets an AI agent read appliances, the machines and shares they protect, snapshot history with local and screenshot verification, the latest verification screenshot, offsite (cloud) replication, alerts across the fleet and the partner portal activity log. It is read-only.

• Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

• Stateless and multi-tenant: the key pair arrives on every request as HTTP headers and is never stored; every tool is listed from the first tools/list

• Python 3.12, uv, FastMCP, httpx

• License: Apache-2.0, Copyright 2026 MSPbots.ai

Authentication headers

Where to get them: in the Datto partner portal open Admin -> Integrations, choose the REST API option and create an API key; the portal shows the public key and the secret key.

How the keys are sent to Datto: every call is a GET to https://api.datto.com/v1/... with HTTP Basic authentication (public key as user name, secret key as password).

A request to /mcp without both headers gets HTTP 401 naming the missing one.

Related MCP server: CyberQP MCP Server

Tools

All tools return JSON except datto_bcdr_get_screenshot, which returns a PNG image. Appliances are addressed by serialNumber; the agentId of the asset tools is the asset's volume name (the name / volume field from datto_bcdr_list_assets). Datto timestamps are Unix seconds; the tools add ISO 8601 ...At fields next to them.

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "unauthorized", "message": "Datto returned HTTP 401 for bcdr/device", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error. Every call is a read, so 429, 5xx and network errors are retried with backoff (honouring Retry-After). Datto's documented limit is 10,000 requests per hour per organization.

Run locally

uv sync
uv run python -m datto_bcdr_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t datto-bcdr-mcp:dev .
docker run --rm -p 8080:8080 datto-bcdr-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). The keys are never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Datto-BCDR-Public-Key: your-public-key" \
  -H "X-Datto-BCDR-Private-Key: your-private-key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# snapshots of one protected server
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-Datto-BCDR-Public-Key: your-public-key" \
  -H "X-Datto-BCDR-Private-Key: your-private-key" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"datto_bcdr_list_backups","arguments":{"serialNumber":"your-serial","agentId":"SRV01"}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

• Tool count (10). Kept as is because the tool names are an existing contract.

• Built on the documented endpoints. Older versions called routes that are not in Datto's API contract (.../asset/{id}/backup, .../screenshot, .../screenshot/{epoch}, .../offsite). This version uses only documented routes: snapshots and screenshot results come from the asset record's backups, the image from .../screenshot/latest, offsite state from the device and asset records.

• datto_bcdr_get_screenshot. The API serves only the latest screenshot, so epoch is now optional; when given, it must match the latest screenshot's time or the tool says which time is available.

• No interactive prompts. Older versions asked the user for a serial number or date window mid-call, which a stateless gateway cannot relay. datto_bcdr_list_assets now requires serialNumber, and the alert / activity tools default to the last 7 days.

• Fleet alerts. datto_bcdr_list_alerts reads the alerts of every appliance whose alert count is not zero (up to 1,000 appliances, 5 at a time) and pages the combined result.

License

Apache License 2.0 - see LICENSE and NOTICE.