
Connects Claude to your Datto RMM account for managing devices, alerts, sites, and jobs across your MSP infrastructure. You get device listing and lookup, alert viewing and resolution, site management, quick job execution, and device audit data retrieval including software inventory. Supports all six regional Datto platforms from South Africa to Australia. Built to work with MCP Gateway for credential handling, though it runs standalone via Docker or npm with API key and secret as environment variables. Reach for this when you need to query fleet status, respond to alerts, or pull audit data without switching between Claude and the Datto console.
MCP server for Datto RMM, enabling Claude to interact with your Datto RMM account.
[!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.
- Create a GitHub Personal Access Token with the
read:packagesscope (classic token). Any GitHub account works — you do not need to be a member of thewyre-technologyorg to read its public packages.- Add it as a build variable when prompted by the deploy flow:
- Cloudflare Workers → set a build variable named
NODE_AUTH_TOKENto your PAT (Workers → Settings → Build → Variables and Secrets).- DigitalOcean App Platform → set an encrypted env var named
GITHUB_TOKENwith 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-ai/datto-rmm-mcp).
datto_get_alert 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 MCP_BRAND_* env vars; plain-JSON behavior is unchanged in other hostsThis server is designed to work with the MCP Gateway which handles authentication and credential management.
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 start
The 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.
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.
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 |
| Tool | Description |
|---|---|
datto_list_devices | List devices with optional site filter |
datto_find_device | Find a device by hostname (exact or partial match) and resolve its UID |
datto_get_device | Get device details by UID |
datto_list_alerts | List open alerts with optional site filter |
datto_get_alert | Get alert details by UID (renders as an interactive card in MCP Apps hosts) |
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 pull ghcr.io/wyre-ai/datto-rmm-mcp:latest
docker run -p 8080:8080 \
-e DATTO_API_KEY=xxx \
-e DATTO_API_SECRET=xxx \
-e DATTO_PLATFORM=concord \
ghcr.io/wyre-ai/datto-rmm-mcp:latest
The image is public and pulls anonymously, so this path needs no GitHub token at all.
The build installs @wyre-technology/node-datto-rmm from GitHub Packages, which
requires a token even though the package is public (see
One-Click Deployment). The Dockerfile takes it as the
GITHUB_TOKEN build arg — omit it and the build fails at npm ci with
npm error 401 Unauthorized ... npm.pkg.github.com:
docker build --build-arg GITHUB_TOKEN=$(gh auth token) -t datto-rmm-mcp .
docker run -p 8080:8080 \
-e DATTO_API_KEY=xxx \
-e DATTO_API_SECRET=xxx \
-e DATTO_PLATFORM=concord \
datto-rmm-mcp
The token is written to a temporary .npmrc that is deleted in the same layer, so
it is never baked into the image.
[!NOTE] The image defaults to
MCP_TRANSPORT=httpon port 8080, so-p 8080:8080is required to reach it. Health check:curl http://localhost:8080/health.
Apache-2.0
DATTO_API_KEY*secretDatto RMM API key
DATTO_API_SECRET*secretDatto RMM API secret key
DATTO_PLATFORMdefault: concordDatto RMM API platform/zone: pinotage, merlot, concord, vidal, zinfandel, or syrah
MCP_TRANSPORTdefault: stdioTransport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
AUTH_MODEdefault: envCredential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
LOG_LEVELdefault: infoLog verbosity: debug, info, warn, error
adelaidasofia/graph-query-mcp