How to integrate Domotz MCP with Hermes

Applies a device profile (a saved bundle of sensors, and optionally credentials) to one or more devices.

Attach a driver to a device.

Attach a sensor to a device.

Bind an existing alert rule to a collector.

Bind an existing alert rule to a specific device.

Bind a Collector to an Organization (addressed by its internal `id`).

Bind tags to a device or to a collector, setting which tags it carries.

Returns the discovery dashboard data for a collector, including initial discovery progress, device statistics, collector issues, and device categories.

Fetch a high-level overview of a collector including its identity, health status, software version, uptime/downtime intervals, device counts, security issues, speed test results, and IP conflict status.

Compares two configuration backup snapshots of the same device.

Create an alert rule.

Add a Contact to the Organization with the given internal `id`.

Create a new Organization for the calling account.

Create a new user-defined tag.

Power-cycle a single outlet on a host device (PoE switch / PDU).

Delete an alert rule by ID.

Permanently delete a Contact from the Organization with the given internal `id`.

PERMANENTLY delete one or more device records from a collector: the device and its history are removed entirely.

Permanently delete a driver from the account.

Permanently delete an Organization.

Delete a user-defined tag by ID.

Remove the binding between a driver and a device on the given collector.

Detach a preconfigured (overlay) sensor from a device.

Returns detailed information about a single device: identity, status, capabilities, protocol coverage, attached sensors/drivers/profiles, OS info, location, power source, and end-of-life (EOL) status for firmware, software, and hardware.

Fetch device performance metrics including round-trip delay, packet loss, uptime, SNMP sensor values, and disk usage over the last 7 days.

Run an action of a driver against a device.

Returns identity and account context for the currently authenticated user: user ID, email, billing state, trial end date, whether the user is the account owner, and whether RBAC is enabled.

Return the set of values available for filtering Domotz audit logs: the operation categories (each with its operation types), source applications, target entities, actor entities, and outcome statuses currently present in the data.

List alert rules bound to a specific collector, including bindings at the collector level and bindings to variables owned by that collector.

Inspect what the customer's Collector can actually run.

Collector-wide credential audit.

Returns a single configuration backup snapshot's text for a device.

Lists devices on a collector that have configuration backup ('config backup') enabled, with the active backup driver, mode (READ_WRITE / READ_ONLY / AVAILABLE / INSUFFICIENT_PRIVILEGE / ERROR), status (ENABLED / DISABLED), failed-inspection count, and last inspection time.

Shows an interactive form to create a new custom tag, with a name field and a color picker.

List alert rules bound to a specific device, including device-level bindings and bindings to variables owned by that device.

Retrieve alert and monitoring configuration status for a specific device.

Per-device credential status drill-down.

Returns the per-device History / Event Log for a single device: the chronological stream of events the device generated, most recent first.

Lists the SNMP-collected interfaces on a device.

Fetch summarised time-series analytics for one or more named metrics on a device within a time range.

Lists the account-wide catalog of drivers available for attaching and executing on devices.

Fetch a single driver template, including its full JS code body and requirement metadata (`requirements.

Returns traffic counters for one or more device interfaces over a time range.

Fetch what a collector actually scans, to answer 'why isn't this device discovered?

Get the full details of a single Organization by its internal `id`: name, `organization_id` (the caller-facing reference), its Contacts, and the ids of the Collectors bound to it.

Shows an interactive form to set or update SNMP credentials on a specific device.

Returns uptime stats for a collector or device over a time range: total uptime percentage, online_seconds, total_seconds, and the list of downtime intervals.

Static analysis of a driver's JS against the Domotz sandbox.

Lists alert rule definitions in the account.

Enumerate the metrics available on a collector — speed-test thresholds, IP-conflict status, collector uptime, security-issues counts, and the rest of the collector-scoped metric catalog.

List the user's notification channels (email, webhook, Slack, etc.

Lists configuration backup snapshots for a device on a collector, newest first.

Lists drivers currently attached to a device.

List everything monitorable on a device.

Lists device profiles in the account.

Lists the sensors currently attached to a device, merged across CUSTOM_OID, TCP, CUSTOM_DRIVER, and PRECONFIGURED kinds.

Returns the device-type catalog used to classify devices (router, switch, AP, server, etc.

List shared driver templates the account can start from.

List the evaluation functions (e.

List the account's Organizations with their Contacts and bound Collector ids.

Returns the account-wide catalog of preconfigured sensors available to attach via `attach_sensor(sensor_spec={kind: 'overlay', overlay_id: .

Returns the account-wide catalog of user-defined tags applied to devices and collectors.

List alert rules that could be bound to a specific device variable.

Add or remove an external host on a collector.

Manage the collector's forced IP scan policy: extra addresses the collector must probe on top of what it discovers by itself.

Add, update or remove a routed network on a collector.

Returns the network topology discovered by a single collector: device-to-device links and per-outlet (port) details.

Permanently resolve one or more alert incidents.

Create or update a driver on the account.

Search alert history with filters.

Search Domotz audit logs for the caller's organization.

Search and list Domotz collectors with filtering and pagination (zero-based: first page is page=0).

Cross-account device search with filters and pagination (zero-based: first page is page=0).

List and filter the organizations visible to the calling user.

Set the collector's DEFAULT SNMP credentials — the ones used for devices that have no SNMP credentials of their own.

Set or overwrite a device credential.

Change the power state of a device: turn it `on`, hold it `off`, `cycle` it, or issue a `software_reboot`.

Set which of the collector's own network interfaces take part in discovery, by name.

Snooze (temporarily mute) all alerting for a collector for a maintenance window.

Submit feedback about a gap in available MCP tools or data.

Unbind an alert rule from a collector.

Unbind an alert rule from a device.

Unbind a Collector from an Organization (addressed by its internal `id`).

Resume alerting on a collector immediately, cancelling any active snooze/maintenance window set by `snooze_collector_alerts`.

Update an existing alert rule in place, preserving its device/collector/variable bindings and alert history (unlike deleting and recreating).

Update editable metadata on a collector (the on-site monitoring agent).

Update how the collector monitors, as opposed to what it monitors.

Update a Contact on the Organization with the given internal `id`.

Update editable metadata fields on a device: `name`, `importance` (important or not important), `zone`, `room`, `serial`, `notes` (max 256 chars).

Manage or unmanage one or more devices by changing their monitoring state.

Update an existing Organization by its internal `id`.

Rename an existing user-defined tag, change its colour, or both.