Server data from the Official MCP Registry
MCP server for Datto RMM — devices, alerts, sites, jobs, and audit data.
MCP server for Datto RMM — devices, alerts, sites, jobs, and audit data.
This Datto RMM MCP server has a well-structured architecture with proper credential handling via environment variables and appropriate use of the MCP SDK. However, there are several concerns: credentials are read from process.env without explicit validation, sensitive data (API keys/secrets) pass through environment variables which could be logged, user input from elicitation flows lacks sanitization before being used in API calls, and the HTTP gateway mode extracts credentials from request headers without proper validation. The codebase is clean and dependencies are reasonable for the category, but input validation and credential security practices need improvement. Supply chain analysis found 3 known vulnerabilities in dependencies (1 critical, 1 high severity).
6 files analyzed · 11 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: DATTO_API_KEY
Environment variable: DATTO_API_SECRET
Environment variable: DATTO_PLATFORM
Environment variable: MCP_TRANSPORT
Environment variable: AUTH_MODE
Environment variable: LOG_LEVEL
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-wyre-technology-datto-rmm-mcp": {
"env": {
"AUTH_MODE": "your-auth-mode-here",
"LOG_LEVEL": "your-log-level-here",
"DATTO_API_KEY": "your-datto-api-key-here",
"MCP_TRANSPORT": "your-mcp-transport-here",
"DATTO_PLATFORM": "your-datto-platform-here",
"DATTO_API_SECRET": "your-datto-api-secret-here"
},
"args": [
"-y",
"@wyre-technology/datto-rmm-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
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-technology/datto-rmm-mcp).
This 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_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 build -t datto-rmm-mcp .
docker run -e DATTO_API_KEY=xxx -e DATTO_API_SECRET=xxx -e DATTO_PLATFORM=concord datto-rmm-mcp
Apache-2.0
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.