oci ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4stdioApache-2.0updated 8d ago
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.
O que dá para fazer com Datto BCDR?
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 (renders as an interactive card in MCP Apps hosts) |
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.
Features
- Interactive Device Card (MCP Apps, SEP-1865):
datto_bcdr_get_devicerenders 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 viawindow.__BRAND__injection orMCP_BRAND_*env vars; plain-JSON behavior is unchanged in other hosts. Editui/and runnpm run build:uito regenerate the embedded card bundle.
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-KeyX-Datto-BCDR-Private-KeyX-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 start
Run as HTTP for testing:
MCP_TRANSPORT=http npm start
curl http://localhost:8080/health
Docker
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
Instalação
Adicione Datto BCDR ao seu cliente. Escolha o que você usa.
claude mcp add ghcr-io-wyre-technology-datto-bcdr-mcp-v -- docker run -i --rm ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4codex mcp add ghcr-io-wyre-technology-datto-bcdr-mcp-v -- docker run -i --rm ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4amp mcp add ghcr-io-wyre-technology-datto-bcdr-mcp-v -- docker run -i --rm ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4{
"mcpServers": {
"ghcr-io-wyre-technology-datto-bcdr-mcp-v": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"ghcr-io-wyre-technology-datto-bcdr-mcp-v": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"ghcr-io-wyre-technology-datto-bcdr-mcp-v","command":"docker","args":["run","-i","--rm","ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"ghcr-io-wyre-technology-datto-bcdr-mcp-v": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"ghcr-io-wyre-technology-datto-bcdr-mcp-v": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"ghcr-io-wyre-technology-datto-bcdr-mcp-v": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"ghcr-io-wyre-technology-datto-bcdr-mcp-v": {
"type": "local",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"ghcr-io-wyre-technology-datto-bcdr-mcp-v": {
"command": {
"path": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4"
]
}
}
}
}Add to your Zed `settings.json`.
docker run -i --rm ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4Run `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
10 ferramentas
Datto BCDR expõe 10 ferramentas a um agente conectado.
- datto_bcdr_list_devices
- List all SIRIS/Alto appliances in the partner portal
- datto_bcdr_get_device
- Get appliance details by `serialNumber` (renders as an interactive card in MCP Apps hosts)
- 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)
Pontuação
83 / 100
Excelente
- Documentação22/25
- Manutenção25/25
- Confiança16/20
- Capacidade8/15
- Instalação12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 1 days ago
- Has a release history
- Repository is not archived
- Licensed Apache-2.0
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 10 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Histórico de versões
| Versões | Publicada |
|---|---|
| 1.1.4Mais recente | 20 de ago. de 2026 |
| 1.1.3 | 10 de ago. de 2026 |
| 1.1.2 | 7 de ago. de 2026 |
| 1.1.1 | 29 de jul. de 2026 |
| 1.1.0 | 17 de jul. de 2026 |
| 1.0.9 | 15 de jul. de 2026 |
| 1.0.8 | 11 de jun. de 2026 |
| 1.0.7 | 29 de mai. de 2026 |
| 1.0.2 | 21 de mai. de 2026 |
| 1.0.1 | 1 de mai. de 2026 |