Datto SaaS Protection

io.github.WYRE-AI由 GitHub 账号 WYRE-AI 发布v3.0.1更新于 Oct 24, 2026

MCP server for Datto SaaS Protection — customers, seats, backup status, bulk seat licensing.

已验证STDIO仅桌面云端与基础设施商业与电商

概览

AI 生成的概览

将 Datto SaaS Protection 备份数据提供给助手：列出受保护的客户与域、查看席位与备份状态，并批量变更席位授权

可以做什么
列出受保护的客户与域，并返回其他工具所需的客户 ID 与订阅 ID。列出并查看席位，在 MCP Apps 宿主中显示只读的交互式席位卡片。列出受保护的应用程序，并按客户查看详细备份统计。批量授权、暂停或取消授权席位，操作前会请求确认。
适用场景
适合通过 Datto SaaS Protection 管理 Microsoft 365 与 Google Workspace 备份的托管服务商或管理员，希望助手在不打开门户的情况下检查备份状况或调整席位授权。
运行要求
以本地 stdio 进程运行（Docker 镜像或 npm 构建）。需要从合作伙伴门户获取 Datto REST API 公钥与密钥对，设置为 DATTO_SAAS_PUBLIC_KEY 和 DATTO_SAAS_SECRET_KEY，并需访问 api.datto.com 的网络。HTTP 模式还需 CONDUIT_S2S_SECRET 和 X-Gateway-S2S 请求头；网关模式从请求头读取凭据。
安装前请注意
批量席位变更工具被标记为写入且具破坏性，可批量授权、暂停或取消授权席位，影响计费与保护状态；执行前会请求确认。Datto 密钥对属于机密凭据。网关模式下凭据通过 X-Datto-SaaS-Public-Key 和 X-Datto-SaaS-Secret-Key 请求头逐次传入。MCP_ALLOW_INSECURE_DEV 会关闭 S2S 校验，仅限本地开发使用。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Datto SaaS Protection，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Datto SaaS Protection MCP Server

[CI] [License: Apache 2.0]

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_seat renders as an interactive card in MCP Apps hosts (Claude Desktop/web) — read-only, showing seat type and Datto seat state; neutral by default, brandable via window.__BRAND__ injection or MCP_BRAND_* env vars; plain-JSON behavior is unchanged in other hosts

Tools

ToolDatto endpointAnnotations
datto_saas_list_domainsGET /v1/saas/domainsread-only
datto_saas_list_seatsGET /v1/saas/{saasCustomerId}/seatsread-only
datto_saas_get_seatGET /v1/saas/{saasCustomerId}/seats (filtered to one seat)read-only
datto_saas_list_applicationsGET /v1/saas/{saasCustomerId}/applicationsread-only
datto_saas_get_backup_statsGET /v1/saas/{saasCustomerId}/detailedBackupStatsread-only
datto_saas_bulk_seat_changePUT /v1/saas/{saasCustomerId}/{externalSubscriptionId}/bulkSeatChangewrite, destructive (asks for confirmation)

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_activity and get_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.

VariableRequiredDescription
DATTO_SAAS_PUBLIC_KEYFor stdio and AUTH_MODE=envDatto REST API public key
DATTO_SAAS_SECRET_KEYFor stdio and AUTH_MODE=envDatto REST API secret key
MCP_TRANSPORTNostdio (default) or http
AUTH_MODENogateway (Docker image and Compose) or env. Gateway mode requires X-Datto-SaaS-Public-Key and X-Datto-SaaS-Secret-Key on each /mcp request and never falls back to DATTO_SAAS_*. env uses those variables only after S2S auth succeeds. Unset means env.
CONDUIT_S2S_SECRETYes for HTTPService-to-service secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder (changeme, secret, replace-me, your-s2s-secret, replace-with-a-real-secret, and the other example values, plus an unresolved ${...} template). Generate one with openssl rand -hex 32. Compose will not start without it. The value is never logged.
MCP_ALLOW_INSECURE_DEVNoSet to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, does not enforce X-Gateway-S2S, and binds 127.0.0.1 only. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) is overridden and that override is logged. A known placeholder secret still refuses to start.
MCP_HTTP_HOSTNoBind address when a real CONDUIT_S2S_SECRET is set. Unset defaults to 127.0.0.1. The container image and Compose set 0.0.0.0 inside the container.
MCP_HTTP_PORTNoHTTP port. Defaults to 8080.

/health stays unauthenticated and does not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.

Local (env mode)

sh
export DATTO_SAAS_PUBLIC_KEY="..."export DATTO_SAAS_SECRET_KEY="..."

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.

bash
TS=$(date +%s)SIG=$(printf 't=%s' "$TS" | openssl dgst -sha256 -hmac "$CONDUIT_S2S_SECRET" -hex | awk '{print $NF}')curl -sS http://127.0.0.1:8080/mcp \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -H "X-Gateway-S2S: t=${TS},v1=${SIG}" \  -H "X-Datto-SaaS-Public-Key: $DATTO_SAAS_PUBLIC_KEY" \  -H "X-Datto-SaaS-Secret-Key: $DATTO_SAAS_SECRET_KEY" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Run

sh
npm installnpm run buildnpm start                       # stdioCONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" MCP_TRANSPORT=http npm start

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:

sh
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 a real S2S secret. In gateway mode, Datto credentials arrive on each request as headers; they are not read from the environment.

bash
docker build -t datto-saas-protection-mcp .docker run \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -p 127.0.0.1:8080:8080 \  datto-saas-protection-mcp

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:

bash
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up

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.

bash
docker run \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -e AUTH_MODE=env \  -e DATTO_SAAS_PUBLIC_KEY=your-public-key \  -e DATTO_SAAS_SECRET_KEY=your-secret-key \  -p 127.0.0.1:8080:8080 \  datto-saas-protection-mcp

License

Apache 2.0 — see LICENSE.

来源：README.md，提交 a843e8a

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

3
  1. v3.0.1最新Oct 14, 2026
  2. v3.0.0Oct 8, 2026
  3. v2.1.5Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分