Datto EDR MCP Server
Integrates with Datto EDR (formerly Infocyte) to search agents, triage alerts, review target groups, organizations, locations, scans, tasks, rules, and extensions, and to perform confirmed high-impact host actions such as scanning or isolating a host.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Datto EDR MCP Server Show me today's alerts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Datto EDR MCP Server
A Model Context Protocol (MCP) server for Datto EDR (formerly Infocyte). It lets AI assistants search agents, triage alerts, review target groups, organizations and locations, follow scans and tasks, read rules and extensions, and — only with explicit confirmation — scan or isolate a host.
It is built, packaged and configured the same way as the WYRE-AI MSP servers
(autotask-mcp, itglue-mcp, datto-rmm-mcp, huntress-mcp): same stdio / Streamable HTTP
transports, same /mcp and /health endpoints on port 8080, same AUTH_MODE=gateway
header injection and X-Gateway-S2S service-to-service check. See
docs/REFERENCE_NOTES.md.
Quick Start
git clone https://github.com/FouadHELLAL7/datto-edr-mcp.git
cd datto-edr-mcp
npm install
npm run buildClaude Desktop / Claude Code (stdio):
{
"mcpServers": {
"datto-edr": {
"command": "node",
"args": ["/path/to/datto-edr-mcp/dist/index.js"],
"env": {
"DATTO_EDR_URL": "https://yourcompany.infocyte.com",
"DATTO_EDR_API_TOKEN": "your-api-token"
}
}
}
}Claude Code CLI:
claude mcp add datto-edr -e DATTO_EDR_URL=https://yourcompany.infocyte.com -e DATTO_EDR_API_TOKEN=your-api-token -- node /path/to/datto-edr-mcp/dist/index.jsThen ask: "Test the Datto EDR connection", "Which agents haven't checked in for 14 days?", "Show me today's alerts".
Related MCP server: Action1 MCP Server
Features
36 tools across 7 domains, all prefixed
datto_edr_LoopBack filtering: every list tool takes
where,limit,skip,order,fieldsPagination: default 50, max 1000 (the API's cap), responses include
hasMore/nextSkipAPI discovery:
datto_edr_api_modelsreads the instance's own/explorer/swagger.jsonSafe writes: scan / isolate / restore / response tools are marked
⚠ HIGH-IMPACTwithdestructiveHint, do nothing withoutconfirm: true, and disappear withDATTO_EDR_READ_ONLY=trueErrors that explain themselves: 401 (bad/expired token), 403 (role), 404, 429 (retried with
Retry-After/ backoff), timeouts, unreachable hostToken hygiene: sent only in the
Authorizationheader, never in URLs, logs or tool outputGateway ready: stateless Streamable HTTP, per-request credentials, fail-closed S2S auth
All logs on stderr, so stdio JSON-RPC is never corrupted
Table of Contents
Installation
Option 1: MCPB Bundle (Claude Desktop)
Download datto-edr-mcp.mcpb from the latest release
and open it with Claude Desktop, or build it yourself with npm run pack:mcpb. Claude Desktop
asks for the instance URL and token (stored as a sensitive value).
Option 2: Docker
docker pull ghcr.io/fouadhellal7/datto-edr-mcp:latestSee Docker Deployment.
Option 3: From Source
npm install
npm run build
node dist/index.js # stdioRequires Node.js 20 or later.
Getting a Datto EDR API token
Sign in to Datto EDR.
Admins: Profile > Admin > Users & Tokens > API Tokens. Other users: Profile > My Settings > API Tokens.
Click Create new token, enter a description, click Create.
Click the hash to copy it. It is shown once; store it in your password manager.
Tokens expire one year after creation and need a user with administrator, analyst or external
analyst access. The instance URL is the address you open in the browser, for example
https://yourcompany.infocyte.com (without /api). Its API explorer is at
https://yourcompany.infocyte.com/explorer/.
Configuration
Variable | Default | Description |
| — | Instance base URL, e.g. |
| — | API token (stdio, or HTTP with |
|
|
|
|
| HTTP credential source: |
| — | Required for HTTP. Shared secret for the |
| — |
|
|
| HTTP port |
|
| HTTP bind address (image sets |
|
|
|
| — | Comma-separated host suffixes the instance URL must match, e.g. |
|
| Per-request timeout |
|
|
|
Gateway mode
Add this server to your MCP gateway exactly like the WYRE connectors:
Value | |
Image |
|
Transport | Streamable HTTP, stateless, JSON responses |
MCP endpoint |
|
Health |
|
Container env |
|
Headers on every /mcp request:
Header | Content |
|
|
| Tenant's instance URL, e.g. |
| Tenant's API token |
Behaviour, identical to the WYRE servers:
No/invalid
X-Gateway-S2S→401. MissingX-Datto-EDR-*header in gateway mode →401, with no fallback to environment credentials.Each request gets a fresh MCP server inside an AsyncLocalStorage credential scope, so tenants never share a token.
The process refuses to start HTTP when
CONDUIT_S2S_SECRETis empty or a placeholder (changeme,secret, ...), unlessMCP_ALLOW_INSECURE_DEV=1.
Because the instance URL arrives in a header, set DATTO_EDR_ALLOWED_HOSTS=.infocyte.com (or
your own domains) on the container so the server only ever calls Datto EDR hosts.
Tools
Call datto_edr_navigate with a domain for a guided list; every tool is always callable.
Domain | Tool | What it does | API |
navigation |
| List the tools of a domain | — |
navigation |
| Credentials configured? read-only? (no API call) | — |
system |
| Live connection/token check, API version |
|
system |
| List models / show a model's properties and paths |
|
system |
| Read-only escape hatch (GET only; credential/token models refused) |
|
system |
| User activity / audit log |
|
agents |
| Search agents: hostname (exact/contains), IP, active, authorized, last seen |
|
agents |
| One agent |
|
agents |
| Count agents with the same filters |
|
alerts |
| Alerts newest first: date range, archived, archive table, |
|
alerts |
| One alert |
|
alerts |
| Count alerts |
|
alerts |
| Enriched alert records |
|
targets |
| Target groups |
|
targets |
| Discovered hosts per target group |
|
organizations |
| Organizations (tenants) | resolved from swagger |
organizations |
| Locations | resolved from swagger |
organizations |
| Integrations | resolved from swagger |
scans |
| Scans |
|
scans |
| User tasks (scan/response progress) |
|
scans |
| Per-host results of a task |
|
scans |
| Background jobs |
|
scans |
| ⚠ Scan one host (needs |
|
scans |
| ⚠ Run a response extension on one host |
|
scans |
| ⚠ Isolate a host ("Host Isolation" extension) |
|
scans |
| ⚠ Undo isolation ("Host Isolation Restore") |
|
rules |
| Detection rules |
|
rules |
| Collection and response extensions |
|
rules |
| Action types |
|
Every endpoint was verified against the official InfocyteHUNTAPI PowerShell module, the Datto EDR help, or other public clients (docs/DATTO_EDR_API.md). Organizations, Locations and Integrations have no public client, so those tools look the model up in the instance's swagger at call time instead of guessing a path. Closing alerts is not implemented because no verified endpoint exists.
Filtering example (alerts from one day with high severity, only some fields):
{
"start_time": "2026-10-28T00:00:00Z",
"end_time": "2026-10-29T00:00:00Z",
"where": { "severity": "high" },
"fields": ["id", "name", "hostname", "createdOn"],
"limit": 100
}Field names differ between instance versions; check them with
datto_edr_api_models {"model": "Alerts"}.
Docker Deployment
cp .env.example .env
# Set CONDUIT_S2S_SECRET. Leave it empty in the example; never commit a real value.
docker compose up -d
curl http://localhost:8080/healthHTTP, gateway mode (what the gateway runs):
docker run -d -p 127.0.0.1:8080:8080 -e CONDUIT_S2S_SECRET=$(openssl rand -hex 32) -e DATTO_EDR_ALLOWED_HOSTS=.infocyte.com ghcr.io/fouadhellal7/datto-edr-mcp:latestHTTP, single tenant (credentials from env):
docker run -d -p 127.0.0.1:8080:8080 -e AUTH_MODE=env -e CONDUIT_S2S_SECRET=... -e DATTO_EDR_URL=https://yourcompany.infocyte.com -e DATTO_EDR_API_TOKEN=... ghcr.io/fouadhellal7/datto-edr-mcp:lateststdio (for Claude Desktop through Docker):
{
"mcpServers": {
"datto-edr": {
"command": "docker",
"args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT=stdio", "-e", "DATTO_EDR_URL", "-e", "DATTO_EDR_API_TOKEN", "ghcr.io/fouadhellal7/datto-edr-mcp:latest"],
"env": {
"DATTO_EDR_URL": "https://yourcompany.infocyte.com",
"DATTO_EDR_API_TOKEN": "your-api-token"
}
}
}
}Development
npm install
npm run dev # tsup --watch
npm run lint # tsc --noEmit + destructive-warning lint
npm run build
npm start # stdio
# HTTP refuses to start until CONDUIT_S2S_SECRET is set
MCP_TRANSPORT=http CONDUIT_S2S_SECRET=$(openssl rand -hex 32) node dist/http.js
# Local HTTP only, without a service-to-service secret (always binds 127.0.0.1)
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 node dist/http.jsMCP Inspector:
npx @modelcontextprotocol/inspector -e DATTO_EDR_URL=https://yourcompany.infocyte.com -e DATTO_EDR_API_TOKEN=your-api-token node dist/index.jsDATTO_EDR_ALLOW_HTTP=1 allows an http:// instance URL, for local mock APIs only.
Testing
npm test
npm run test:coverageThe suite (vitest, mocked fetch) covers the client (auth header, retries, error mapping,
token redaction, URL validation), every domain tool's request and filter, the write-tool
confirm and read-only gates, MCP tool listing, and the HTTP transport (health, S2S, gateway
header isolation). CI also builds the Docker image and smoke-tests it in HTTP and stdio mode.
What to test against a live instance
No real Datto EDR token was available while building this server. Run these with a token (read-only first):
datto_edr_test_connection— token and URL work.datto_edr_api_models— swagger is readable; note the real names of the Organizations, Locations and Integrations models and the Agent/Alert property names.datto_edr_agents_listwithhostname_contains— confirms theilikeoperator (if it errors, usewhere: {"hostname": {"like": "%name%"}}), andlast_seen_beforeconfirms theheartbeatfield.datto_edr_alerts_listwith a date range, thendatto_edr_alert_details_list.datto_edr_organizations_list,datto_edr_locations_list,datto_edr_integrations_list.datto_edr_extensions_list {"name":"Host Isolation"}— the isolation extension exists.Only on a test machine:
datto_edr_isolate_hostwithconfirm: true, follow it withdatto_edr_tasks_get, thendatto_edr_restore_host.
License
Apache-2.0
Available Tools
36 toolsdatto_edr_action_types_listCRead-only
List the response/action types the instance supports (GET /api/ActionTypes).
Inputs: skip, limit, order, where, +1 more.
datto_edr_addresses_listARead-only
List discovered host addresses (GET /api/Addresses), optionally within one target group. Shows whether each host was reachable and which agent it maps to.
Inputs: ip, skip, limit, order, +5 more.
datto_edr_agents_countARead-only
Count agents matching the same filters as datto_edr_agents_list (GET /api/Agents/count). Useful for "how many agents are offline" questions.
Inputs: ip, where, active, hostname, +4 more.
datto_edr_agents_getARead-only
Get one Datto EDR agent by id (GET /api/Agents/{id}).
Inputs: id (required).
datto_edr_agents_listARead-only
List or search Datto EDR endpoint agents (GET /api/Agents). Filter by hostname, IP, active/authorized state and last heartbeat; add any other property (OS, version, isolation state...) through "where" after checking field names with datto_edr_api_models {"model":"Agents"}. Paged with limit/skip.
Inputs: ip, skip, limit, order, +8 more.
datto_edr_alert_details_listARead-only
List enriched alert records (GET /api/AlertDetails), which join alert, host and file/rule context. Use "where" to filter (e.g. by alert id or hostname) and "fields" to keep the response small.
Inputs: skip, limit, order, where, +1 more.
datto_edr_alerts_countARead-only
Count alerts matching the same filters as datto_edr_alerts_list (GET /api/Alerts/count).
Inputs: where, end_time, start_time, archive_table, +1 more.
datto_edr_alerts_getARead-only
Get one Datto EDR alert by id (GET /api/Alerts/{id}).
Inputs: id (required), archive_table.
datto_edr_alerts_listARead-only
List Datto EDR alerts, newest first (GET /api/Alerts). Filter by creation date range and archived state; filter by severity, host, organization, status or any other property through "where" (see datto_edr_api_models {"model":"Alerts"} for this instance's field names). Set archive_table for alerts older than 30 days.
Inputs: skip, limit, order, where, +5 more.
datto_edr_api_modelsARead-only
List the API models this Datto EDR instance exposes (read from its /explorer/swagger.json), or pass "model" to see that model's paths and properties. Use it to find filterable field names before building a "where" filter.
Inputs: model.
datto_edr_audit_log_listCRead-only
List user activity (audit log) entries (GET /api/useractivities).
Inputs: skip, limit, order, where, +2 more.
datto_edr_extensions_getBRead-only
Get one extension by id (GET /api/extensions/{id}).
Inputs: id (required).
datto_edr_extensions_listARead-only
List Datto EDR extensions (GET /api/extensions): collection extensions and response actions such as "Host Isolation" and "Host Isolation Restore". Extension ids/names feed datto_edr_run_response.
Inputs: name, skip, limit, order, +2 more.
datto_edr_integrations_listARead-only
List configured integrations (RMM, PSA, RocketCyber...). The endpoint is looked up in this instance's /explorer/swagger.json; if it is missing, the error lists related models to query with datto_edr_raw_request.
Inputs: skip, limit, order, where, +1 more.
datto_edr_isolate_hostADestructive
⚠ HIGH-IMPACT: Network-isolate one host by running the "Host Isolation" response extension. The host keeps talking to Datto EDR but loses all other network access until restored (Windows and Linux). Requires confirm: true.
Inputs: target (required), target_group_id (required), confirm.
datto_edr_jobs_listBRead-only
List background jobs (GET /api/jobs). Pass state "active" for running jobs.
Inputs: skip, limit, order, state, +2 more.
datto_edr_locations_getARead-only
Get one Datto EDR location by id. The endpoint is looked up in this instance's /explorer/swagger.json; if it is missing, the error lists related models to query with datto_edr_raw_request.
Inputs: id (required).
datto_edr_locations_listARead-only
List Datto EDR locations (sites inside organizations). Filter by organization through "where" once you know the field name (datto_edr_api_models). The endpoint is looked up in this instance's /explorer/swagger.json; if it is missing, the error lists related models to query with datto_edr_raw_request.
Inputs: skip, limit, order, where, +1 more.
datto_edr_organizations_getARead-only
Get one Datto EDR organization by id. The endpoint is looked up in this instance's /explorer/swagger.json; if it is missing, the error lists related models to query with datto_edr_raw_request.
Inputs: id (required).
datto_edr_organizations_listARead-only
List Datto EDR organizations (tenants/customers). The endpoint is looked up in this instance's /explorer/swagger.json; if it is missing, the error lists related models to query with datto_edr_raw_request.
Inputs: skip, limit, order, where, +1 more.
datto_edr_raw_requestARead-only
Read-only escape hatch for Datto EDR API endpoints not covered by a typed tool. Prefer typed tools. Sends GET https:///api/; the token is added automatically. Object values in "query" are JSON-encoded, so pass a LoopBack filter as {"filter":{"where":{...},"limit":50}} or a count as path "Model/count" with {"where":{...}}. Credential and token models are refused.
Inputs: path (required), query.
datto_edr_restore_hostADestructive
⚠ HIGH-IMPACT: Remove network isolation from one host by running the "Host Isolation Restore" response extension. Requires confirm: true.
Inputs: target (required), target_group_id (required), confirm.
datto_edr_rules_getARead-only
Get one detection rule by id (GET /api/rules/{id}).
Inputs: id (required).
datto_edr_rules_listBRead-only
List Datto EDR detection rules (GET /api/rules).
Inputs: name, skip, limit, order, +2 more.
datto_edr_run_responseADestructive
⚠ HIGH-IMPACT: Run a response extension (e.g. kill process, isolate, collect evidence) on one host (POST /api/targets/scan with the extension). Identify the extension by id or exact name. Requires confirm: true; without it, returns the request it would send.
Inputs: target (required), target_group_id (required), confirm, arguments, +2 more.
datto_edr_scan_hostADestructive
⚠ HIGH-IMPACT: Start a forensic scan of one host (POST /api/targets/scan). Runs on the endpoint and uses its resources. Requires confirm: true; without it, returns the request it would send. Returns a task id for datto_edr_tasks_get.
Inputs: target (required), target_group_id (required), confirm, options.
datto_edr_scans_getBRead-only
Get one scan by id (GET /api/scans/{id}).
Inputs: id (required).
datto_edr_scans_listARead-only
List Datto EDR scans (GET /api/scans), optionally for one target group.
Inputs: skip, limit, order, where, +2 more.
datto_edr_statusARead-only
Check whether Datto EDR credentials are configured and list the available domains. Does not call the API; use datto_edr_test_connection for a live check.
Inputs: no named parameters.
datto_edr_target_groups_getARead-only
Get one target group by id (GET /api/targets/{id}).
Inputs: id (required).
datto_edr_target_groups_listARead-only
List Datto EDR target groups (GET /api/targets). Target groups hold the hosts that scans and response actions run against; their ids are needed by datto_edr_scan_host and the response tools.
Inputs: name, skip, limit, order, +2 more.
datto_edr_task_items_listARead-only
List the per-host items of a user task (GET /api/userTaskItems), e.g. the result of a scan or response on each host.
Inputs: task_id (required), skip, limit, order, +2 more.
datto_edr_tasks_getARead-only
Get one user task by id, including status, progress and message (GET /api/usertasks/{id}). Use it to follow a scan or response started by this server.
Inputs: id (required).
datto_edr_tasks_listARead-only
List user tasks (scans, responses, enumerations shown in the task list), newest first (GET /api/usertasks). Use status "Active" for running tasks.
Inputs: skip, type, limit, order, +4 more.
datto_edr_test_connectionARead-only
Test the connection and token against the Datto EDR instance (GET /api/Version). Returns the instance host and API version.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 36 tools
Most tools target a distinct resource (agents, alerts, scans, tasks, rules, extensions) and descriptions clarify boundaries, but some pairs overlap: datto_edr_isolate_host and datto_edr_restore_host are specializations of datto_edr_run_response, and tasks/jobs/task_items/scans are easy to confuse at a glance. Alert_details_list versus alerts_list also requires reading descriptions to distinguish.
Nearly everything follows datto_edr_<resource>_<verb> in snake_case with a small predictable verb set (_list, _get, _count). The main deviation is verb-first ordering for action tools (isolate_host, restore_host, scan_host, run_response) versus noun-first for read tools, but the pattern remains readable and predictable.
36 tools is heavy for a coherent set; many resources get a three-tool pattern (list/get/count) that could be collapsed, and the discovery family (navigate, status, test_connection, api_models, raw_request) adds further surface. The domain is broad, but the count exceeds what an agent can comfortably select from.
Read coverage is strong across all major resources, and high-impact response actions exist (isolate, restore, scan, run_response), but there is no write lifecycle: no alert status/archive update, no rule creation or modification, and the raw_request escape hatch is read-only. These are notable gaps for an agent expected to manage rather than just observe.
Maintenance
Related MCP Connectors
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
Deltabridge brings an AI-native cyber threat intelligence platform into your AI agent. Search a knowledge graph of 400,000+ threat actors, malware families, vulnerabilities, indicators and campaigns, mapped to MITRE ATT&CK. Look up and enrich IOCs, trace links between entities and read living briefs built from 300+ open sources. Read-only, scoped to your organisation, with OAuth sign-in or an API key. Included on Researcher, Business and Enterprise plans.
Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.
- DNS-DATA RemoteDeprecatedcom.dns-data
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
Related MCP Servers
- AlicenseBqualityBmaintenanceEnables AI assistants to gain read-only visibility into an ESET PROTECT fleet via the ESET Connect API, covering devices, detections/EDR, vulnerabilities, patch status, and users.26Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI assistants to query an Action1 RMM tenant for organizations, endpoints, groups, missing updates, vulnerabilities, automations, reports, users, and roles, and to build custom PowerShell-based reports whose results can be requeryed and read back. It also runs one-off PowerShell diagnostics as SYSTEM on selected Windows endpoints and allows limited report-related changes, while leaving endpoints, users, and organizations untouched.332MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read Datto SIRIS and ALTO backup appliance data, including protected machines and shares, snapshot history with local and screenshot verification, offsite replication status, fleet alerts, and partner portal activity logs. Provides read-only access to the Datto partner REST API with stateless, per-request authentication.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read protected computers and their check-ins, computer groups, approval requests, the unified audit log, and child organizations through a zero-trust endpoint security portal API. Every operation is read-only, with credentials supplied per request as headers and never stored.Apache 2.0