Datto BCDR MCP server
MCP server for Datto BCDR — appliances, agents, recovery points, screenshots, alerts.
0 stars
Reviews
Write oneNobody has reviewed Datto BCDR yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Datto BCDR tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Datto BCDR compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 70/100
- higher than 35% of 48,255 servers
Release history: 2 versions in the registry since 2026-08-26, latest 2026-10-14, typically one every 49 days.
Install Datto BCDR in Claude Code, Cursor or VS Code
claude mcp add datto-bcdr-mcp -- docker run -i --rm ghcr.io/wyre-ai/datto-bcdr-mcp:v1.1.6
What the publisher says
From the Datto BCDR repository's README, as published. We do not edit it. Read it 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
When the user omits required filters (date range, serial number, etc.) the server uses MCP elicitation to prompt for them.
Features
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 MCPBRAND env vars; plain-JSON behavior is unchanged in other hosts. Edit ui/ and run npm run build:ui to regenerate the embedded card bundle.
- Interactive Device Card (MCP Apps, SEP-1865): dattobcdrget_device
Configuration
Environment-variable mode (default)
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
npm install
npm run build
DATTO_BCDR_PUBLIC_KEY=... DATTO_BCDR_PRIVATE_KEY=... npm startRun as HTTP for testing:
MCP_TRANSPORT=http npm start
curl http://localhost:8080/healthDocker
docker build -t datto-bcdr-mcp .
docker run --rm -p 8080:8080 \
-e DATTO_BCDR_PUBLIC_KEY=... \
-e DATTO_BCDR_PRIVATE_KEY=... \
datto-bcdr-mcpLicense
Apache-2.0
Nothing above is checked by us. What we check is on the safety report.
Datto BCDR: common questions
- Is Datto BCDR MCP server safe?
- Mostly: it is graded B (70/100). Read the Datto BCDR safety report
- How do I install Datto BCDR?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Datto BCDR need an API key?
- Yes. The registry entry asks for
DATTO_BCDR_PUBLIC_KEY,DATTO_BCDR_PRIVATE_KEY. - Is Datto BCDR maintained?
- The last commit was 6 days ago (2026-10-29). The latest release is v1.1.6.