
Datto BCDR
io.github.wyre-technology由 GitHub 帳號 wyre-technology 發布v1.1.4更新於 Oct 24, 2026
MCP server for Datto BCDR — appliances, agents, recovery points, screenshots, alerts.
概覽
面向 Datto BCDR 備份入口網站的唯讀 MCP 伺服器,讓助理檢視設備、受保護代理、復原點、截圖驗證與警示。
- 可以做什麼
- 列出並檢視 SIRIS/Alto 設備及依序號的詳細資料
- 列出設備上的受保護代理並取得單一代理
- 列出代理的復原點與截圖驗證,並取得截圖影像
- 檢視設備的異地同步狀態
- 依日期範圍列出入口網站警示與活動記錄
- 在缺少日期範圍或序號等篩選條件時提示使用者補充
- 適用情境
- 適合託管服務供應商或備份管理員讓助理查詢 Datto BCDR 備份狀況:有哪些設備、代理是否受保護、最近復原點時間、異地同步是否正常,以及有哪些未處理警示。
- 執行需求
- 以本機 stdio 程序執行(Docker 映像或 npm 建置)。需要 Datto BCDR 合作夥伴入口網站 API 憑證,即 DATTO_BCDR_PUBLIC_KEY 與 DATTO_BCDR_PRIVATE_KEY,可選 DATTO_BCDR_REGION(us 或 eu)。HTTP 模式另需 CONDUIT_S2S_SECRET 與 X-Gateway-S2S 標頭;閘道模式從 X-Datto-BCDR-Public-Key 與 X-Datto-BCDR-Private-Key 標頭讀取憑證。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Datto BCDR,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
Datto BCDR MCP Server
[Release] [License: Apache 2.0]
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
- 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
Copy .env.example and set the variables below. The stdio
transport reads DATTO_BCDR_* and is not affected by HTTP service-to-service
auth.
/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=<unix seconds>,v1=<hex hmac-sha256>. The signed message is the ASCII string t=<unix seconds> (the same timestamp prefix), and the HMAC key is CONDUIT_S2S_SECRET. Timestamps more than 300 seconds from the server clock are rejected.
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:
Local development
HTTP refuses to start until CONDUIT_S2S_SECRET is set:
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:
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.
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:
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses DATTO_BCDR_PUBLIC_KEY and DATTO_BCDR_PRIVATE_KEY:
License
Apache-2.0
來源:README.md,提交 c0e0580
工具
0版本歷史
1- v1.1.4最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分