
Datto SaaS Protection
io.github.WYRE-AI由 GitHub 帳號 WYRE-AI 發布v3.0.2更新於 Nov 22, 2026
MCP server for Datto SaaS Protection — customers, seats, backup status, bulk seat licensing.
概覽
針對 Datto SaaS Protection 的 MCP 伺服器,讓助理列出受保護的客戶與網域、檢視席次與備份狀態,並批次變更席次授權。
- 可以做什麼
- 列出受保護的客戶與網域,回傳其他工具所需的客戶與訂閱 ID
- 列出並檢視席次,包括單一席次的類型與保護狀態
- 列出受保護的應用程式,並依客戶檢視詳細備份統計
- 批次授權、暫停或取消授權席次,執行前需確認
- 適用情境
- 適合託管服務商或 IT 管理員透過 AI 助理查核 Microsoft 365 與 Google Workspace 的備份涵蓋範圍與席次保護狀況,或在不開啟 Datto 入口網站的情況下批次調整席次授權。
- 執行需求
- 以本機 stdio 程序執行(Node.js 建置或已發佈的容器映像)。需要從合作夥伴入口網站取得 Datto REST API 公鑰/密鑰組,透過 DATTO_SAAS_PUBLIC_KEY 與 DATTO_SAAS_SECRET_KEY 設定,並需連線 api.datto.com。HTTP 託管另需 CONDUIT_S2S_SECRET,閘道模式下還需每次請求攜帶憑證標頭。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Datto SaaS Protection,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
Datto SaaS Protection MCP Server
A Model Context Protocol server exposing the Datto SaaS Protection (Backupify) API to Claude and other MCP clients.
What it does
Surfaces SaaS backup posture for your Microsoft 365 and Google Workspace
customers to AI assistants, using the documented Datto REST API
(https://api.datto.com/v1/saas/...): list protected customers/domains,
inspect seats and their protection state, review backup status per
application, and (with confirmation) license, pause or unlicense seats in bulk.
- Interactive Seat Card (MCP Apps):
datto_saas_get_seatrenders as an interactive card in MCP Apps hosts (Claude Desktop/web) — read-only, showing seat type and Datto seat state; neutral by default, brandable viawindow.__BRAND__injection orMCP_BRAND_*env vars; plain-JSON behavior is unchanged in other hosts
Tools
Start with datto_saas_list_domains: it returns the saasCustomerId and
externalSubscriptionId every other tool needs.
Earlier versions exposed
list_clients,list_backups,queue_restore,get_restore_status,list_activityandget_license_usage. Those were built on routes Datto does not serve (/v1/saas/clients,/restores, …) and always returned 404, so they are removed.
Credentials
Create an API key in the Datto Partner Portal (Admin > Integrations > API
Keys). The API uses HTTP Basic auth with the public/secret key pair. There is a
single API host (api.datto.com); there is no regional (EU) API host.
Copy .env.example and set the variables below.
/health stays unauthenticated and does not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.
Local (env mode)
Hosted (gateway mode)
The WYRE MCP Gateway injects credentials per request via headers:
X-Datto-SaaS-Public-Key(required, secret)X-Datto-SaaS-Secret-Key(required, secret)X-Datto-SaaS-Region(accepted for backward compatibility; ignored)
A request missing the public or secret key gets HTTP 401 and does not fall back to DATTO_SAAS_PUBLIC_KEY / DATTO_SAAS_SECRET_KEY in the process environment.
HTTP authentication
With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. The check is verifyS2sHeader in src/s2s-verify.ts: the header value is t=<unix seconds>,v1=<hex>, where the hex is HMAC-SHA256 of the literal string t=<unix seconds> keyed with CONDUIT_S2S_SECRET (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock. A missing or invalid header is HTTP 401, before vendor credentials are read.
Run
HTTP refuses to start until CONDUIT_S2S_SECRET is a real secret. Local HTTP without one is development-only and binds 127.0.0.1:
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 a real 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. The gateway service sets AUTH_MODE=gateway, does not inject DATTO_SAAS_PUBLIC_KEY or DATTO_SAAS_SECRET_KEY, and publishes 127.0.0.1:8080:8080:
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses DATTO_SAAS_PUBLIC_KEY and DATTO_SAAS_SECRET_KEY. It is separate from the gateway Compose service above.
License
Apache 2.0 — see LICENSE.
來源:README.md,提交 a843e8a
工具
0版本歷史
4- v3.0.2最新Nov 21, 2026
- v3.0.1Oct 14, 2026
- v3.0.0Oct 8, 2026
- v2.1.5Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分