Datto BCDR

Name: Datto BCDR
Author: wyre-technology

作者：wyre-technology版本 1.1.4i★ –i在你的电脑上运行

注册名称io.github.wyre-technology/datto-bcdr-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：DATTO_BCDR_PUBLIC_KEY, DATTO_BCDR_PRIVATE_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： DATTO_BCDR_PUBLIC_KEY, DATTO_BCDR_PRIVATE_KEY, DATTO_BCDR_REGION, MCP_TRANSPORT, AUTH_MODE, LOG_LEVEL

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

Docker已安装 Docker

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "datto-bcdr": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "DATTO_BCDR_PUBLIC_KEY",
        "-e",
        "DATTO_BCDR_PRIVATE_KEY",
        "-e",
        "DATTO_BCDR_REGION",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4"
      ],
      "env": {
        "DATTO_BCDR_PUBLIC_KEY": "your-value",
        "DATTO_BCDR_PRIVATE_KEY": "your-value",
        "DATTO_BCDR_REGION": "your-value",
        "MCP_TRANSPORT": "your-value",
        "AUTH_MODE": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add datto-bcdr --env DATTO_BCDR_PUBLIC_KEY=your-value --env DATTO_BCDR_PRIVATE_KEY=your-value --env DATTO_BCDR_REGION=your-value --env MCP_TRANSPORT=your-value --env AUTH_MODE=your-value --env LOG_LEVEL=your-value -- docker run -i --rm -e DATTO_BCDR_PUBLIC_KEY -e DATTO_BCDR_PRIVATE_KEY -e DATTO_BCDR_REGION -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "datto-bcdr": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "DATTO_BCDR_PUBLIC_KEY",
        "-e",
        "DATTO_BCDR_PRIVATE_KEY",
        "-e",
        "DATTO_BCDR_REGION",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4"
      ],
      "env": {
        "DATTO_BCDR_PUBLIC_KEY": "your-value",
        "DATTO_BCDR_PRIVATE_KEY": "your-value",
        "DATTO_BCDR_REGION": "your-value",
        "MCP_TRANSPORT": "your-value",
        "AUTH_MODE": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "datto-bcdr": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "DATTO_BCDR_PUBLIC_KEY",
        "-e",
        "DATTO_BCDR_PRIVATE_KEY",
        "-e",
        "DATTO_BCDR_REGION",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-technology/datto-bcdr-mcp:v1.1.4"
      ],
      "env": {
        "DATTO_BCDR_PUBLIC_KEY": "your-value",
        "DATTO_BCDR_PRIVATE_KEY": "your-value",
        "DATTO_BCDR_REGION": "your-value",
        "MCP_TRANSPORT": "your-value",
        "AUTH_MODE": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

DATTO_BCDR_PUBLIC_KEY 机密必填 env
Datto BCDR partner portal public API key
DATTO_BCDR_PRIVATE_KEY 机密必填 env
Datto BCDR partner portal private API key
DATTO_BCDR_REGION env
Region: 'us' (default) or 'eu'
MCP_TRANSPORT env
Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
AUTH_MODE env
Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
LOG_LEVEL env
Log verbosity: debug, info, warn, error

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 wyre-technology 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18475 个服务器的 0%
发布到注册中心的时间比此分类中其他 18475 个服务器的 28% 更新
基础检查结果等于或优于此分类中其他 18475 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Datto BCDR 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：DATTO_BCDR_PUBLIC_KEY, DATTO_BCDR_PRIVATE_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.1.4）于3个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Tethered Trust

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者：formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

安装

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者：desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

安装

Tethered Trust

Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.

作者：tetheredtrust.com非常新今天更新

在云端运行✓ tetheredtrust.com

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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_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.

Variable	Required	Description
`DATTO_BCDR_PUBLIC_KEY`	For stdio and `AUTH_MODE=env`	Datto BCDR partner portal public key
`DATTO_BCDR_PRIVATE_KEY`	For stdio and `AUTH_MODE=env`	Datto BCDR partner portal private key (secret)
`DATTO_BCDR_REGION`	No	`us` (default) or `eu`
`MCP_TRANSPORT`	No	`stdio` (default) or `http`
`AUTH_MODE`	No	`gateway` (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_SECRET`	Yes for HTTP	Service-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_DEV`	No	Set 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_HOST`	No	Bind 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_PORT`	No	HTTP 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= ,v1= . The signed message is the ASCII string t= (the same timestamp prefix), and the HMAC key is CONDUIT_S2S_SECRET. Timestamps more than 300 seconds from the server clock are rejected.

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:

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

npm install

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

HTTP refuses to start until CONDUIT_S2S_SECRET is set:

CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" MCP_TRANSPORT=http npm start

curl 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:

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.

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:

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:

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