# Datto RMM (oci · ghcr.io/wyre-ai/datto-rmm-mcp)

MCP server for Datto RMM — devices, alerts, sites, jobs, and audit data.

- Trust score: 51/100 (low)
- Change this week: +42
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- oci · `ghcr.io/wyre-ai/datto-rmm-mcp`: 51/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-datto-rmm-mcp/ghcr-io-wyre-ai-datto-rmm-mcp.md), [page](https://verifymcp.io/servers/wyre-ai-datto-rmm-mcp/ghcr-io-wyre-ai-datto-rmm-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/datto-rmm-mcp`
- Version: `v1.10.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1301 tokens (~68/item across 19 items; 18 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Datto RMM MCP server?

Datto RMM runs locally as a container image, launched with docker run --rm -i -e DATTO_API_KEY -e DATTO_API_SECRET -e DATTO_PLATFORM -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/datto-rmm-mcp:v1.10.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add wyre-ai-datto-rmm-mcp -- docker run --rm -i -e DATTO_API_KEY -e DATTO_API_SECRET -e DATTO_PLATFORM -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/datto-rmm-mcp:v1.10.1
```

This image reads DATTO_API_KEY, DATTO_API_SECRET, DATTO_PLATFORM, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-datto-rmm-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DATTO_API_KEY",
        "-e",
        "DATTO_API_SECRET",
        "-e",
        "DATTO_PLATFORM",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/datto-rmm-mcp:v1.10.1"
      ]
    }
  }
}
```

This image reads DATTO_API_KEY, DATTO_API_SECRET, DATTO_PLATFORM, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "wyre-ai-datto-rmm-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DATTO_API_KEY",
        "-e",
        "DATTO_API_SECRET",
        "-e",
        "DATTO_PLATFORM",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/datto-rmm-mcp:v1.10.1"
      ]
    }
  }
}
```

This image reads DATTO_API_KEY, DATTO_API_SECRET, DATTO_PLATFORM, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add wyre-ai-datto-rmm-mcp -- docker run --rm -i -e DATTO_API_KEY -e DATTO_API_SECRET -e DATTO_PLATFORM -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/datto-rmm-mcp:v1.10.1
```

This image reads DATTO_API_KEY, DATTO_API_SECRET, DATTO_PLATFORM, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-datto-rmm-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "DATTO_API_KEY",
        "-e",
        "DATTO_API_SECRET",
        "-e",
        "DATTO_PLATFORM",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/datto-rmm-mcp:v1.10.1"
      ],
      "enabled": true
    }
  }
}
```

This image reads DATTO_API_KEY, DATTO_API_SECRET, DATTO_PLATFORM, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  wyre-ai-datto-rmm-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "DATTO_API_KEY", "-e", "DATTO_API_SECRET", "-e", "DATTO_PLATFORM", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/datto-rmm-mcp:v1.10.1"]
```

This image reads DATTO_API_KEY, DATTO_API_SECRET, DATTO_PLATFORM, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-datto-rmm-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DATTO_API_KEY",
        "-e",
        "DATTO_API_SECRET",
        "-e",
        "DATTO_PLATFORM",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/datto-rmm-mcp:v1.10.1"
      ]
    }
  }
}
```

This image reads DATTO_API_KEY, DATTO_API_SECRET, DATTO_PLATFORM, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "wyre-ai-datto-rmm-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DATTO_API_KEY",
        "-e",
        "DATTO_API_SECRET",
        "-e",
        "DATTO_PLATFORM",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/datto-rmm-mcp:v1.10.1"
      ]
    }
  }
}
```

This image reads DATTO_API_KEY, DATTO_API_SECRET, DATTO_PLATFORM, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 49, +40)

- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.47
- [functional] Package version: v1.9.0 → v1.10.1

### 2026-10-14 (score 9, 0)

- [functional] Package version: v1.9.0 → v1.10.1

### 2026-10-13 (score 9, 0)

- [functional] Package version: v1.9.0 → v1.10.0

### 2026-10-10 (score 9, 0)

- [functional] Package version: v1.9.0 → v1.10.0

### 2026-10-07 (score 9, −34)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional] Package version: v1.9.0 → v1.10.0

### 2026-10-01 (score 43)

First indexed and scored.

## MCP tools (18)

### `datto_list_devices` (~78 tokens)

List all devices in Datto RMM. Can filter by site. To look up a single device by hostname, use datto_find_device instead.

Input parameters:

- `max` (number): Maximum number of results (default: 50)
- `siteUid` (string): Filter devices by site UID (optional - if omitted, returns all devices)

### `datto_find_device` (~132 tokens)

Find a device by hostname and return its UID plus a lightweight summary. Use this before datto_get_device when the user provides a hostname instead of a UID.

Input parameters:

- `exactMatch` (boolean): Require an exact (case-insensitive) hostname match. Set to false for partial/substring matching. Defaults to true.
- `hostname` (string, required): Hostname to search for, for example APP-HV-HOST06
- `max` (number): Maximum number of matching devices to return (default: 25)
- `siteUid` (string): Optional site UID to narrow the hostname lookup to one site

### `datto_get_device` (~50 tokens)

Get full details for a specific device by its UID. If you only have a hostname, call datto_find_device first to resolve the UID.

Input parameters:

- `deviceUid` (string, required): The device UID

### `datto_list_alerts` (~59 tokens)

List open alerts. Can filter by site.

Input parameters:

- `max` (number): Maximum number of results (default: 50)
- `siteUid` (string): Filter alerts by site UID (optional - if omitted, returns all account alerts)

### `datto_get_alert` (~31 tokens)

Get details for a specific alert by its UID

Input parameters:

- `alertUid` (string, required): The alert UID

### `datto_resolve_alert` (~31 tokens)

Resolve an alert by its UID

Input parameters:

- `alertUid` (string, required): The alert UID to resolve

### `datto_list_sites` (~33 tokens)

List all sites in the account

Input parameters:

- `max` (number): Maximum number of results (default: 50)

### `datto_get_site` (~31 tokens)

Get details for a specific site by its UID

Input parameters:

- `siteUid` (string, required): The site UID

### `datto_list_components` (~226 tokens)

List components (the scripts/monitors available to run as quick jobs) in the account, optionally filtered by a case-insensitive substring of the name. Use this to find a componentUid for datto_run_quickjob — otherwise there's no way to get one short of the Datto RMM web UI. Each result's `variables` lists what datto_run_quickjob's `variables` map needs to be filled in with to run that component. A quickjob HTTP 500 usually means the API user's security role is below the component's Level (Datto returns 500 where 403 belongs). The API does not expose component Level; check it in the RMM web UI under the component's settings before blaming the payload.

Input parameters:

- `max` (number): Maximum number of results (default: 50)
- `name` (string): Case-insensitive substring filter on component name, e.g. "disk" or "cleanup". Applied across every page of the account's component catalogue before truncating to max, so a match on a later page isn'…

### `datto_run_quickjob` (~139 tokens)

Run a quick job on a device. Returns a job UID — pass it to datto_get_job, datto_get_job_components, datto_get_job_results, datto_get_job_stdout, and datto_get_job_stderr to check the job's status and retrieve its output, since this call itself is fire-and-forget.

Input parameters:

- `componentUid` (string, required): UID of the component to run
- `deviceUid` (string, required): The device UID to run the job on
- `jobName` (string, required): Name for the quick job
- `variables` (object): Variables to pass to the job (key-value pairs)

### `datto_get_job` (~76 tokens)

Get status and details for a quick job by its UID (e.g. queued/running/completed, device count, timestamps). Use this after datto_run_quickjob to check whether the job finished and how it went.

Input parameters:

- `jobUid` (string, required): The job UID, returned by datto_run_quickjob

### `datto_get_job_components` (~39 tokens)

Get the components (scripts/actions and their variables) that make up a quick job

Input parameters:

- `jobUid` (string, required): The job UID

### `datto_get_job_results` (~83 tokens)

Get the result of a quick job on one specific device — status, exit code, timing, and error message if it failed. Use datto_get_job first if you need to find which devices the job ran on.

Input parameters:

- `deviceUid` (string, required): The device UID to get the job result for
- `jobUid` (string, required): The job UID

### `datto_get_job_stdout` (~65 tokens)

Get the captured stdout output of a quick job on a specific device. Use this to diagnose what a script actually printed when a quick job's outcome is unclear.

Input parameters:

- `deviceUid` (string, required): The device UID
- `jobUid` (string, required): The job UID

### `datto_get_job_stderr` (~58 tokens)

Get the captured stderr output of a quick job on a specific device. Use this to diagnose why a quick job failed.

Input parameters:

- `deviceUid` (string, required): The device UID
- `jobUid` (string, required): The job UID

### `datto_get_device_audit` (~63 tokens)

Get audit data for a device (hardware, software, OS information)

Input parameters:

- `auditType` (string): Type of audit: 'full' for complete audit or 'software' for software inventory only
- `deviceUid` (string, required): The device UID

### `datto_get_device_patches` (~51 tokens)

Get Windows patch installation status for a device - per-patch installed/missing/pending status, severity, reboot requirement, and KB article

Input parameters:

- `deviceUid` (string, required): The device UID

### `datto_get_site_patches` (~35 tokens)

Get Windows patch installation status across all devices in a site

Input parameters:

- `siteUid` (string, required): The site UID

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-datto-rmm-mcp/ghcr-io-wyre-ai-datto-rmm-mcp#diagnostics

## Score history

- 2026-10-18: 51
- 2026-10-17: 50
- 2026-10-16: 50
- 2026-10-15: 49
- 2026-10-14: 9
- 2026-10-13: 9
- 2026-10-12: 9
- 2026-10-10: 9
- 2026-10-07: 9
- 2026-10-04: 43
- 2026-10-03: 43
- 2026-10-02: 43
- 2026-10-01: 43

## Common questions

### What is the Datto RMM MCP server?

Datto RMM is an MCP server listed in the public MCP registry as io.github.WYRE-AI/datto-rmm-mcp. MCP server for Datto RMM, devices, alerts, sites, jobs, and audit data. This page covers its container image (ghcr.io/wyre-ai/datto-rmm-mcp).

### Is the Datto RMM MCP server safe to use?

Datto RMM scores 51 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Datto RMM MCP server expose?

Datto RMM exposes 18 tools: datto_list_devices, datto_find_device, datto_get_device, datto_list_alerts, datto_get_alert, and 13 more. Their descriptions and schemas cost roughly 1,280 tokens of context every time the server is loaded.

### Is the Datto RMM MCP server still maintained?

Datto RMM is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Datto RMM MCP server under?

Datto RMM declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/wyre-ai/datto-rmm-mcp
- Repository: https://github.com/WYRE-AI/datto-rmm-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-datto-rmm-mcp/ghcr-io-wyre-ai-datto-rmm-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-datto-rmm-mcp/ghcr-io-wyre-ai-datto-rmm-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-datto-rmm-mcp/ghcr-io-wyre-ai-datto-rmm-mcp