Datto SaaS Protection

io.github.wyre-technologyPublished by GitHub account wyre-technologyv2.1.4Updated Oct 24, 2026

MCP server for Datto SaaS Protection — M365/GWS backups, restores, seats.

VerifiedSTDIODesktop onlyCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant inspect Datto SaaS Protection backup posture for Microsoft 365 and Google Workspace customers and, with confirmation, change seat licensing…

What you can do
This server exposes the documented Datto SaaS Protection (Backupify) REST API to MCP clients. Read-only tools list protected domains, seats, applications and detailed backup statistics, and a seat lookup can render as an interactive card in MCP Apps hosts. One write tool performs bulk seat changes (license, pause or unlicense) and asks for confirmation before acting.
When to use it
Use it when you manage Datto SaaS Protection for Microsoft 365 or Google Workspace tenants and want an assistant to report on protected customers, seat protection state and per-application backup status, or to carry out bulk seat licensing changes.
Requirements
Runs locally as a stdio process (Node.js build and start, or the published container image). Needs a Datto SaaS Protection API key created in the Datto Partner Portal, supplied via DATTO_SAAS_API_KEY in env mode or injected as headers by the WYRE MCP Gateway in gateway mode. AUTH_MODE selects the credential source; DATTO_SAAS_REGION and LOG_LEVEL are optional. Network access to the Datto API is required.
Before you install
The API key is a secret and must be handled as one. The bulk seat change tool is marked write and destructive: it can license, pause or unlicense seats in bulk, affecting billing and customer protection, so confirm targets before running it. The README notes the API uses HTTP Basic auth with a public/secret key pair and that there is no regional EU API host, so the region setting is ignored.

Installation

In SourceWeft

  1. Open Datto SaaS Protection in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

Source: README.md at commit a843e8a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.1.4LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts