Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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-technology/node-datto-rmm, which is hosted on the GitHub Packages npm registry. GitHub Packages has no anonymous access — even though the package is public, everynpm installneeds a token. The cloud builder runsnpm installfor you, so you must give it one, or the build fails withnpm error 401 Unauthorized ... npm.pkg.github.com.
>
1. Create a GitHub Personal Access Token with theread:packagesscope (classic token). Any GitHub account works — you do not need to be a member of thewyre-technologyorg 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 `NODE_AUTH_TOKEN` to your PAT (Workers → Settings → Build → Variables and Secrets). - DigitalOcean App Platform → set an encrypted env var named `GITHUB_TOKEN` with scope Build Time to your PAT (the.do/deploy.template.yamlalready 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-technology/datto-rmm-mcp).
Features
- Device Management: List, search, and get details for devices
- Alert Management: View and resolve alerts
- 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 NODE_AUTH_TOKEN, so no further config is needed.
Configuration
The server accepts credentials via environment variables:
| Variable | Description |
|---|---|
DATTO_API_KEY | Your Datto RMM API key |
DATTO_API_SECRET | Your Datto RMM API secret |
DATTO_PLATFORM | API platform: pinotage, merlot, concord, vidal, zinfandel, or syrah (default: concord) |
When used with the MCP Gateway, credentials are injected via X_API_KEY and X_API_SECRET environment variables.
Platform Selection
Datto RMM uses regional API endpoints. Select the platform that matches your account:
| Platform | Region/Description |
|---|---|
pinotage | South Africa |
merlot | Europe |
concord | US East (default) |
vidal | Canada |
zinfandel | US West |
syrah | Australia |
Available Tools
| Tool | Description |
|---|---|
datto_list_devices | List devices with optional site filter |
datto_get_device | Get device details by UID |
datto_list_alerts | List open alerts with optional site filter |
datto_resolve_alert | Resolve an alert |
datto_list_sites | List all sites |
datto_get_site | Get site details |
datto_run_quickjob | Run a quick job on a device |
datto_get_device_audit | Get device audit data (full or software only) |
Docker
docker build -t datto-rmm-mcp .
docker run -e DATTO_API_KEY=xxx -e DATTO_API_SECRET=xxx -e DATTO_PLATFORM=concord datto-rmm-mcpLicense
Apache-2.0