Datto BCDR MCP — Claude Code MCP server: what it does, how to install
Syncs Datto BCDR fleet records into a local SQLite database. Helps your AI agent detect stale backups and failed screenshot checks across appliances.
Open on GitHubWhat Datto BCDR MCP does
This server mirrors Datto BCDR fleet telemetry into local SQLite tables. Standard partner portals focus on one appliance at a time, making fleet audits slow. With this tool, your assistant analyzes all client backups together to pinpoint at-risk systems.
Under the hood, tools hand off work to the companion datto-bcdr-cli binary. Both the CLI and the MCP component install via the project setup script or through the Claude Code plugin marketplace.
Do not turn on HTTP transport mode. Current builds lack request timeouts and payload size limits, so you must stick to local stdio.
What it helps with
- locate backups with failed screenshot verification across appliances
- flag stale client backups throughout the entire fleet
- mirror Datto BCDR device states into local SQLite tables
- identify at-risk client systems without clicking through Partner Portal
Example prompts for the agent
- List all Datto BCDR clients with failed screenshot verification
- Which backups are stale across our fleet right now?
- Summarize at-risk client systems based on recent snapshot history
How to install Datto BCDR MCP
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Datto BCDR MCP
How do I install Datto BCDR MCP in Claude Code?
Register the catalog with /plugin marketplace add Servosity/msp-skills, then install the package with /plugin install datto-bcdr@msp-skills. You also need the companion datto-bcdr-cli binary installed via the project shell script.
What does Datto BCDR MCP do?
It replicates backup appliance status into an offline SQLite database. Your coding assistant can query overall fleet health and spot failing screenshot tests.
Can I run this server over HTTP?
No, HTTP transport mode is insecure in this build due to missing request size limits. Stick strictly to standard stdio transport on your local workstation.
