
Datto BCDR MCP
io.github.ServosityPublished by GitHub account Servosityv0.1.10Updated Nov 6, 2026
Sync your whole Datto BCDR fleet into local SQLite and answer the questions the per-appliance
Overview
Local MCP server that mirrors a Datto BCDR fleet into SQLite so an assistant can answer fleet-wide backup health questions.
- What you can do
- Sync Datto BCDR devices, agents, shares and alerts into a local SQLite mirror with full-text search
- Query backup health fleet-wide: failed screenshot verification, stale local or offsite backups, recoverability percentage
- Rank client risk, triage open alerts by client, and project storage runway per appliance
- Surface forgotten assets (paused, archived, offline appliances) and per-client reports for QBRs
- Run read-only lookups on devices, agents, assets, shares, alerts and restore VMs, plus local learning and profile commands
- When to use it
- For MSPs and Datto partners who need cross-client answers the per-appliance Partner Portal cannot give, such as which backups failed verification or which clients are at risk before a QBR or audit. Best when you want the data to stay on your own machine and use a desktop agent that runs local stdio servers.
- Requirements
- Runs as a local process on the user's machine (desktop only), typically via the .mcpb bundle or the companion datto-bcdr-cli binary. Needs a Datto partner public/secret key pair from the Partner Portal, supplied as DATTO_BCDR_PUBLIC_KEY and DATTO_BCDR_SECRET_KEY. DATTO_BCDR_BASE_URL defaults to the standard API host. Network access to the Datto BCDR API for syncing.
Installation
In SourceWeft
- Open Datto BCDR MCP in the dashboard and add it to a workspace.
- 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 BCDR + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP
Unofficial. Community-built Claude Code Skill and MCP server for the Datto BCDR API. Not affiliated with, endorsed by, or sponsored by Datto, Inc..
[Datto BCDR demo - animated preview]
▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.
Also from Servosity. Backup & DR is Servosity's own field - the first-party Servosity connector brings this same fleet-wide, local-mirror approach (fleet attention, stale backups, restores, QBR reporting) to Servosity Backup and DR.
Comparing backup vendors? One of our MSP partners told us, "My guys now spend a tenth of the time on backups." Fixing is included in every Servosity co-managed backup plan, and our engineers tell you what they did. See how co-managed backup works
Sync your whole Datto BCDR fleet into local SQLite and answer the questions the per-appliance Partner Portal can't: which backups failed screenshot verification, which are stale, and which clients are at risk. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.
Works with your agent
Security note (until this connector is reprinted). Do not run HTTP mode (
--transport http), not even on localhost. This build checks a token, but it predates the fix release's request size and time limits. The MCP tools can also read your data with your credentials. Use the default stdio transport. If you set up a tunnel for a remote agent, shut it down. A fix is on the way.
The six agents MSP owners actually use (self-serve, works today):
The ChatGPT desktop app runs datto-bcdr-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Also for the Microsoft and Google stacks
Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly and speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: docs/which-agent.md.
Run more than one agent? Install across all 51+ supported agents in one command:
npx skills add Servosity/msp-skills@latest(requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.
Install in 60 seconds
Fastest for Claude Desktop - one-click .mcpb
Claude Desktop bundle: the
.mcpblaunches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companiondatto-bcdr-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or setDATTO_BCDR_CLI_PATHto an existing binary). Details: #331.
Download Datto BCDR MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Datto BCDR release on the releases page.)
Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:
Path A - paste one prompt into your AI agent (recommended)
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Datto BCDR Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/datto-bcdr/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/datto-bcdr/install.ps1 | iex. Then authenticate per the README and rundatto-bcdr-cli --helpto explore.
The same prompt works in any agent that can run shell.
Path B - run the installer yourself
Windows (PowerShell):
macOS / Linux:
The installer drops both datto-bcdr-cli (the CLI) and datto-bcdr-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
Upgrade to the latest version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
Windows (PowerShell):
Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update datto-bcdr@msp-skills.
Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client
After the installer runs, see mcp-install.md and docs/which-agent.md for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.
Install for Hermes
From the Hermes CLI:
Inside a Hermes chat session:
Hermes speaks MCP natively, so it can also use the datto-bcdr-mcp server directly - same install path, same env vars.
Install for OpenClaw
Tell your OpenClaw agent (copy this):
Install the datto-bcdr skill from https://github.com/servosity/msp-skills/tree/main/skills/datto-bcdr. The skill defines how its required CLI (
datto-bcdr-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Authenticate
Set the credentials the CLI needs (from your Datto BCDR portal):
doctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.
What this skill does
The Datto BCDR API answers one appliance at a time. This skill mirrors every device, agent, share, and alert into local SQLite, then answers the fleet-wide questions the per-appliance Partner Portal can't:
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
What makes this different
Most Datto BCDR integrations and MCP servers proxy each question into a live API call - and because the Datto API is strictly per-appliance, that means one call per device just to answer one fleet question like "which protected machines across all 40 clients failed their last screenshot verification, oldest failures first".
This skill syncs Datto BCDR into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like client-risk, recoverability, and client-report join across devices, agents, alerts, screenshots, and storage in a single pass - work a stateless per-device API wrapper can't do.
The pain this closes
On r/msp, the recurring Datto BCDR complaint isn't that backups fail loudly - it's that they fail quietly. A protected machine's screenshot/boot verification starts failing, or an agent stops taking local snapshots, and nobody notices because the Partner Portal shows backup health one appliance at a time. The gap surfaces at the worst possible moment: restore time, with the client already down. Owners describe walking every SIRIS and ALTO by hand before a QBR or an audit, because the one question they actually need answered - "are all my backups across all my clients recoverable right now?" - has no fleet-wide view.
This skill closes that gap by mirroring the whole estate locally and answering across it:
datto-bcdr-cli screenshots --failed --stale-days 7 --agent- every silently-unbootable backup, fleet-wide, oldest failures first.datto-bcdr-cli recoverability --agent- the single defensible number: what percent of the fleet is fresh and screenshot-verified bootable.datto-bcdr-cli stale-backups --local-days 1 --offsite-days 3 --agent- agents that quietly stopped taking points, before a client needs them.datto-bcdr-cli client-risk --top 10 --agent- which clients to call first, ranked across backups, alerts, and storage.
See pain-point.md for the longer narrative.
Frequently asked questions
Does this work with ChatGPT?
Yes, in the ChatGPT desktop app. It runs MCP servers locally (STDIO), the way datto-bcdr-mcp runs, and shares MCP configuration with Codex (OpenAI): add datto-bcdr-mcp under Settings > MCP servers as a STDIO server, or add it once to Codex's ~/.codex/config.toml. ChatGPT on the web is not supported by msp-skills yet: it needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted; the security note in mcp-install.md explains why. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Does this work with Codex, Cursor, Windsurf, Cline, Copilot, or Gemini?
Yes - all of them speak MCP. Cross-tool install commands are in the matrix above and the deep-dive in docs/which-agent.md.
Do I need to know how to code?
No. The recommended install is to paste one sentence into Claude Code or Codex - your agent reads SKILL.md and does the install. The fallback is a one-line installer per OS (bash or PowerShell). Neither path requires writing code. You'll enter your Datto BCDR credentials once.
Is my Datto BCDR data safe?
Your data stays on your machine. The CLI and MCP server are local binaries. The SQLite mirror sits in a directory under your user account. The AI agent only sees what the CLI returns - typically a query result, not raw bulk data. Credentials are read from your environment or your agent's config; never bundled into this repo or transmitted anywhere by MSP Skills.
Do I need to be a Datto partner to use this?
Yes. It uses the Datto BCDR REST API, which needs a partner-generated public/secret key pair from the Partner Portal under Admin > Integrations. If you manage Datto BCDR appliances you already qualify - the CLI base64-encodes the key pair into the Authorization header on every request.
Will this hit my Datto BCDR API rate limits?
It's gentle by design. The first sync pulls each resource with bounded pagination, and you can cap throughput with --rate-limit. After that, fleet questions run against the local mirror and make zero API calls - --data-source local never touches the API at all.
Does this replace the Datto Partner Portal?
No. It answers the fleet-wide, cross-client questions the per-appliance portal can't, and it's read-only for everyday use. You still use the portal for restores, virtualization, and device configuration.
What does it cost?
Free. Apache-2.0 licensed. You pay only for whichever AI agent you use (Claude, ChatGPT, Codex, etc.), and that's billed by your AI provider, not by us.
Safety model
The strongest control is the scope you grant the Datto BCDR credentials - the CLI can only do what the credentials are permitted to do. Full details, including how to lock it down, are in governance.md.
Status
Live-verified. Confirmed by Abhi Saini, Bearium Networks (MSP) against their own production tenant (receipt). More MSPs run it live in our weekly Build Sessions. RSVP at compoundingteams.com/build-sessions.
Standards. Conforms to the open Agent Skills spec (Anthropic, Dec 2025; 40+ agents). MCP-compatible - works with any MCP-capable agent including Hermes. OpenClaw-ready (frontmatter pre-wired, awaiting OpenClaw launch).
Maintained by Servosity. Apache-2.0 licensed. Built with CLI Printing Press. Last updated: 2026-06-06.
Source: skills/datto-bcdr/README.md at commit 061ec05
Tools
0Version history
5- v0.1.10LatestOct 23, 2026
- v0.1.8Oct 16, 2026
- v0.1.7Oct 14, 2026
- v0.1.6Sep 29, 2026
- v0.1.5Sep 16, 2026
Score
40% 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
Declare a license in the repository or the registry entry.