Skip to content

API Reference

This section contains documentation for all Datto RMM tooling packages.

PackageDescription
MCP ServerAI assistant integration via Model Context Protocol
TypeScript ClientFully typed TypeScript/JavaScript client
Rust ClientNative async Rust client

The MCP server (datto-rmm-mcp-server) enables AI assistants like Claude to interact with Datto RMM through natural language. It exposes 39+ tools for managing:

  • Devices, sites, and alerts
  • Jobs and components
  • Audit data (hardware, software, ESXi, printers)
  • Activity logs and system status

See the MCP Server documentation for configuration and usage.

Both the TypeScript and Rust clients are generated from the Datto RMM OpenAPI specification.

The API provides endpoints for:

  • Account - Account information and settings
  • Sites - Site management and configuration
  • Devices - Device inventory and management
  • Alerts - Alert monitoring and resolution
  • Jobs - Quick job scheduling and monitoring
  • Audit - Device audit data (software, hardware, etc.)
  • Filters - Device filter management
  • Users - User management
  • Activity Logs - Audit trail of actions

All packages use OAuth 2.0 client credentials flow:

  1. Obtain API Key and Secret from your Datto RMM portal (your user profile → API Details)
    • API keys are generated per-user from each user’s profile settings
  2. The client exchanges credentials for an access token
  3. Tokens are cached and automatically refreshed before expiry

The Datto RMM API has rate limits. Check the X-RateLimit-* headers in responses for current limits and usage. The MCP server includes a get-rate-limit tool to check your current status.

All packages support all 6 Datto RMM regional platforms:

  • Pinotage
  • Merlot
  • Concord
  • Vidal
  • Zinfandel
  • Syrah