Datto RMM MCP Server

MCP server for Datto RMM, enabling Claude to interact with your Datto RMM account.

One-Click Deployment

Related MCP server: 3CX MCP Server

Features

• Device Management: List, search, and get details for devices

• Alert Management: View and resolve alerts

• Interactive Alert Card (MCP Apps): 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 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.

Attributing jobs to the end user

Datto RMM records the API account that created a job and offers no way to override it, so on a shared service account every quick job in the console reads as the integration rather than the person who asked for it.

If the gateway sends an X-Mcp-User-Upn header, that identity is appended to the job name, which is the only field that reaches the console's activity list:

Restart Service [someone@example.com]

Only honoured when AUTH_MODE=gateway. Without a gateway in front, the header is whatever the caller chose to send, so attributing a job to it would look authoritative while being self-declared. It is advisory labelling in either case and never affects authorization. Brackets and control characters are stripped from the value, and it is length-capped, so the suffix cannot be forged or made to corrupt the name.

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 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.

Configuration

The server accepts credentials via environment variables:

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:

Available Tools

Tools that only read data from Datto RMM carry annotations: { readOnlyHint: true } in their tools/list definition. Clients that support this MCP hint (e.g. Microsoft 365 Copilot / Copilot Studio) can use it to skip the per-call confirmation prompt for those tools. Tools that create, update, resolve, or run anything are never annotated as read-only.

Docker

Use the prebuilt image (no build, no token)

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.

Build from source

The build installs @wyre-ai/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.

License

Apache-2.0