Skip to content
plugmcp
DirectorySkillsCategoriesBlog
EN/中文
Sign inSign up
Home/Servers/Datto SaaS Protection

Datto SaaS Protection

I
by io.github.WYRE-AI

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

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command
docker run -i --rm ghcr.io/wyre-ai/datto-saas-protection-mcp:v3.0.0
Credentials from the publisher
  • DATTO_SAAS_PUBLIC_KEY — Datto REST API public key (Partner Portal > Admin > Integrations > API Keys)
  • DATTO_SAAS_SECRET_KEY — Datto REST API secret key
  • MCP_TRANSPORT — Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
  • AUTH_MODE — Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
  • LOG_LEVEL — Log verbosity: debug, info, warn, error
Provider
Claude Code
DATTO_SAAS_PUBLIC_KEY=<secret> DATTO_SAAS_SECRET_KEY=<secret> MCP_TRANSPORT=<value> AUTH_MODE=<value> LOG_LEVEL=<value> claude mcp add io.github.wyre-ai-datto-saas-protection-mcp -- docker run -i --rm ghcr.io/wyre-ai/datto-saas-protection-mcp:v3.0.0

Run in a terminal.

Claude Desktop
{
  "mcpServers": {
    "io.github.wyre-ai-datto-saas-protection-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/datto-saas-protection-mcp:v3.0.0"
      ],
      "env": {
        "DATTO_SAAS_PUBLIC_KEY": "<secret>",
        "DATTO_SAAS_SECRET_KEY": "<secret>",
        "MCP_TRANSPORT": "<value>",
        "AUTH_MODE": "<value>",
        "LOG_LEVEL": "<value>"
      }
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

View more
  • Firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
  • N
    NotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
  • Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

Related skills

View all
  • reaReverse engineer anything with agents, from app behavior down to native binaries.
  • rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
  • rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

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

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

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.

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

npm install
npm run build
npm start                       # stdio
CONDUIT_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:

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.

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:

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.

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.

How do I install Datto SaaS Protection?
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Datto SaaS Protection need an API key?
The publisher lists these environment variables: DATTO_SAAS_PUBLIC_KEY, DATTO_SAAS_SECRET_KEY, MCP_TRANSPORT, AUTH_MODE, LOG_LEVEL.
What transport does Datto SaaS Protection use?
Datto SaaS Protection runs locally over stdio.
When was Datto SaaS Protection last checked?
Last checked 2026-10-16. MCP server for Datto SaaS Protection — customers, seats, backup status, bulk seat licensing.

No tool list yet. Remote servers get one after the first health check.

plugmcp

Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.

  • github.com/TODO
  • x.com/TODO
  • linkedin.com/company/TODO

PlugMCP, 2026

Product
  • Browse
  • Install
  • Host your own
  • Voice mode
  • Browser
Directory
  • All MCP servers
  • Agent skills
  • Categories
  • New
  • Voice
  • Submit a server
Developers
  • Docs
  • Blog
  • What is MCP
  • What is WebMCP
  • Status
Company
  • About
  • Contact
  • Terms
  • Privacy
  • DPA