Datto RMM MCP server
MCP server for Datto RMM — devices, alerts, sites, jobs, and audit data.
4 stars
Reviews
Write oneNobody has reviewed Datto RMM yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Datto RMM tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How Datto RMM compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 45% of 48,255 servers
- GitHub stars
- 4
- more than 82% of 28,688 servers
Install Datto RMM in Claude Code, Cursor or VS Code
claude mcp add datto-rmm-mcp -- docker run -i --rm ghcr.io/wyre-technology/datto-rmm-mcp:v1.7.6
What the publisher says
From the Datto RMM repository's README, as published. We do not edit it. Read it on GitHub
Datto RMM MCP Server
MCP server for Datto RMM, enabling Claude to interact with your Datto RMM account.
One-Click Deployment
[!IMPORTANT]
Before you click: this server depends on @wyre-ai/node-datto-rmm,
which is hosted on the GitHub Packages npm registry. GitHub Packages has no
anonymous access — even though the package is public, every npm install needs a
token. The cloud builder runs npm install for you, so you must give it one, or
the build fails with npm error 401 Unauthorized ... npm.pkg.github.com.
1. Create a GitHub Personal Access Token with the read:packages scope
(classic token).
Any GitHub account works — you do not need to be a member of the
wyre-technology org to read its public packages.
2. Add it as a build variable when prompted by the deploy flow:
- Cloudflare Workers → set a build variable named NODEAUTHTOKEN to your PAT
(Workers → Settings → Build → Variables and Secrets).
- DigitalOcean App Platform → set an encrypted env var named GITHUBTOKEN**
with scope Build Time to your PAT (the .do/deploy.template.yaml already declares it).
[!NOTE]
The DigitalOcean target builds the full Docker image and runs the complete MCP
server over HTTP — this is the recommended path for operators. This repo has no
Cloudflare Workers entrypoint (src/worker.ts), so the Workers button is not a
supported target yet; prefer DigitalOcean or the prebuilt container image
(ghcr.io/wyre-ai/datto-rmm-mcp).
Features
- Device Management: List, search, and get details for devices
- Alert Management: View and resolve alerts
- Interactive Alert Card (MCP Apps): dattogetalert renders as an interactive card in MCP Apps hosts (Claude Desktop/web) with an in-card "Resolve alert" round-trip; neutral by default, brandable via window.BRAND injection or MCPBRAND env vars; plain-JSON behavior is unchanged in other hosts
- Site Management: List and view site details
- Quick Jobs: Run quick jobs on devices
- Audit Data: Retrieve full device audit or software inventory
Installation
Via MCP Gateway (Recommended)
This server is designed to work with the MCP Gateway which handles authentication and credential management.
Local Development
This server's @wyre-technology/ dependencies live on the GitHub Packages** npm registry, which requires a token even for public packages. Authenticate once, then install:
# Authenticate npm to GitHub Packages (token needs the read:packages scope)
export NODE_AUTH_TOKEN=$(gh auth token) # or a PAT with read:packages
npm install
npm run build
npm startThe repo's .npmrc already points the @wyre-technology scope at GitHub Packages and reads the token from NODEAUTHTOKEN, so no further config is needed.
Configuration
The server accepts credentials via environment variables:
When used with the MCP Gateway, credentials are injected via XAPIKEY and XAPISECRET environment variables.
Platform Selection
Datto RMM uses regional API endpoints. Select the platform that matches your account:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Datto RMM: common questions
- Is Datto RMM MCP server safe?
- Mostly: it is graded B (75/100). Read the Datto RMM safety report
- How do I install Datto RMM?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Datto RMM need an API key?
- Yes. The registry entry asks for
DATTO_API_KEY,DATTO_API_SECRET. - Is Datto RMM maintained?
- The last commit was 6 days ago (2026-10-29). The latest release is v1.7.6.
- How does Datto RMM compare with other MCP servers?
- safety score 75/100 (higher than 45% of 48,255 servers); github stars 4 (more than 82% of 28,688 servers). Full comparison.