---
title: "Domotz MCP server for AI agents - actionlake"
description: "Give Claude 176 Domotz actions through one MCP server: custom driver associations, devices. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/domotz
updated: 2026-10-23
---

Connectors · MSP & PSA

# Domotz MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Domotz and the rest of your systems. It gives your agent 176 Domotz actions (87 reads, 57 writes and 32 that wait for a confirmation) and holds the Domotz credential itself, so the agent never does. It paces Domotz's limits and records every call.

[Connect Domotz free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "domotz.members.list",
  intent: "check which Domotz account is connected"
}
# User list · read · 1 upstream call
```

- 176 actions in one signed file
- 87 read look, never change
- 57 write create and update
- 32 wait for a yes destructive, confirmed first

Set up

## Connect Domotz in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect Domotz.
   API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
   - `api_key` Domotz API key: in the Domotz Portal open Settings > Services > API Keys and create a key
   - `host` Where your Domotz lives: your host
   ```
   account { op: "connections.requirements", service: "domotz" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "domotz.members.list" }
   # user list · read · 1 upstream call
   check { action: "domotz.members.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Domotz at a glance

**Sign-in**

API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.

**You provide**

`api_key`

**Setup fields**

`host`

**Limits we pace to**

10 calls a second, per connection

**API covered**

Domotz Public API 1 (OpenAPI 3.1), at your Domotz instance's API base URL, which you enter when connecting (path /public-api/v1)

**Built from**

Domotz's documentation, read 23 October 2026[api-us-east-1-cell-1.domotz.com](https://api-us-east-1-cell-1.domotz.com/public-api/v1/meta/open-api-definition) [portal.domotz.com](https://portal.domotz.com/developers/)

**Service file**

Version 1.0.0, signed (Ed25519)

**Cached reads**

87 of 87 reads, for up to 5 minutes; a write clears what it affects

**Shared entities**

5, so ask can line Domotz up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in Domotz.

176 actions in 95 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **87** read look, never change
- **57** write create and update
- **32** destructive wait for a confirmation

1. ### Custom driver associations
   5
   1 read · 3 write · 1 destructive
   Driver device binding · Driver device bindings list · Disabled Drivers reactivation · Driver device binding paramaters update
2. ### Devices
   5
   2 read · 1 write · 2 destructive
   Collector devices list · Device details · Device deletion · Device property change
3. ### Members
   5
   2 read · 2 write · 1 destructive
   User list · User creation · User · User edit
4. ### Organization contacts
   5
   2 read · 2 write · 1 destructive
   List Organization Contacts · Create Organization Contact · Get Organization Contact Details · Update Organization Contact
5. ### Organizations
   5
   2 read · 2 write · 1 destructive
   List Organizations · Create Organization · Get Organization Details · Update Organization
6. ### User groups
   5
   2 read · 2 write · 1 destructive
   User group list · User group creation · User group · User group edit
7. ### Alert rules
   4
   2 read · 2 write · 0 destructive
   Create Alert Rule · List Alert Rules · Get Alert Rule Details · Update Alert Rule
8. ### Custom tags
   4
   1 read · 2 write · 1 destructive
   Tag list · Tag creation · Tag edit · Tag deletion

**87 more areas · 138 actions**

- Alert profile collector bindings **3**
- Alert profile device bindings **3**
- Collector custom tag bindings **3**
- Collector excluded devices **3**
- Collector external host scan policy **3**
- Collector interfaces policy **3**
- Collector ip scan policy **3**
- Collector service ports **3**
- Collector VPN sessions **3**
- Collectors **3**
- Device configurations **3**
- Device custom tag bindings **3**
- Device power outlets **3**
- Device SNMP sensors **3**
- Device TCP sensors **3**
- Inventory fields **3**
- SNMP sensor triggers **3**
- Alert rule collector bindings **2**
- Alert rule contact channel bindings **2**
- Alert rule device bindings **2**
- Alerts **2**
- Collector SNMP authentication **2**
- Collector uptimes **2**
- Custom drivers **2**
- Device inventory fields **2**
- Device power actions **2**
- Device profiles **2**
- Device SNMP authentication **2**
- Inventory **2**
- Organization collector bindings **2**
- Power outlet attachments **2**
- Roles **2**
- SNMP sensor trigger alerts **2**
- Teams **2**
- Alert profiles **1**
- API usage **1**
- Areas **1**
- Audit logs **1**
- Collector activity logs **1**
- Collector alert rules **1**
- Collector connection consumption **1**
- Collector custom driver execution logs **1**
- Collector datapoints **1**
- Collector device applications **1**
- Collector device variables **1**
- Collector DHCP device discovery **1**
- Collector eye statistics **1**
- Collector interfaces **1**
- Collector ip conflicts **1**
- Collector metric statistics **1**
- Collector network topology **1**
- Collector ownership **1**
- Collector routed networks **1**
- Collector RTD stats **1**
- Collector SNMP sensors **1**
- Collector speed tests **1**
- Collector status history **1**
- Collector TCP sensors **1**
- Collector variable history **1**
- Collector variables **1**
- Contact channels **1**
- Current user **1**
- Custom driver actions **1**
- Datapoints **1**
- Device alert rules **1**
- Device applications **1**
- Device base types **1**
- Device configuration backups **1**
- Device connections **1**
- Device credentials **1**
- Device custom driver execution logs **1**
- Device datapoints **1**
- Device detected types **1**
- Device inventory **1**
- Device monitoring state **1**
- Device RTD history **1**
- Device SNMP community **1**
- Device status history **1**
- Device uptimes **1**
- Device variable history **1**
- Device variables **1**
- Down devices **1**
- External hosts **1**
- SNMP sensor history **1**
- SNMP sensor trigger functions **1**
- Unmanaged devices **1**
- User alert profiles **1**

Top actions

## The Domotz API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 33 of Domotz's 33 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `domotz.members.list` User list | User list. | read | `identity.user.list` 474 connectors |
| `domotz.organization_contacts.list` List Organization Contacts | List Organization Contacts. | read | `crm.contact.list` 177 connectors |
| `domotz.members.create` User creation | User creation. | write | `identity.user.create` 262 connectors |
| `domotz.organizations.list` List Organizations | List Organizations. | read | `crm.company.list` 162 connectors |
| `domotz.members.delete` User deletion | User deletion. | destructive | `identity.user.delete` 253 connectors |
| `domotz.organization_contacts.create` Create Organization Contact | Create Organization Contact. | write | `crm.contact.create` 161 connectors |
| `domotz.organizations.create` Create Organization | Create Organization. | write | `crm.company.create` 142 connectors |
| `domotz.user_groups.list` User group list | User group list. | read | `identity.group.list` 262 connectors |
| `domotz.devices.list` Collector devices list | Collector devices list. | read | `device.endpoint.list` 65 connectors |
| `domotz.user_groups.create` User group creation | User group creation. | write | `identity.group.create` 205 connectors |
| `domotz.alerts.list` List Alerts | List Alerts. | read | `monitoring.alert.list` 51 connectors |
| `domotz.roles.list` Role list | Role list. | read | `identity.role.list` 184 connectors |

Try it

## Prompts to paste into Claude.

Each one names the Domotz actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Which Domotz alerts are open right now? Group them by service.
   calls `domotz.alerts.list`
2. Write write
   User creation in Domotz. Show me exactly what you will send before you save it.
   calls `domotz.members.create`
3. Across systems read
   Which Domotz companies have invoices in NetSuite, and how many each?
   calls `domotz.organizations.list` `netsuite.views.invoices`

Across your systems

## Domotz, joined to the rest of your business.

One `ask` fetches from Domotz and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

- Which Domotz companies have invoices in NetSuite, and how many each?
  `domotz.organizations.list` + `netsuite.views.invoices`, on `crm.company` · [NetSuite](https://actionlake.com/connectors/netsuite)
- Which Domotz companies have tickets in HubSpot CRM, and how many each?
  `domotz.organizations.list` + `hubspot_crm.tickets.list`, on `crm.company` · [HubSpot CRM](https://actionlake.com/connectors/hubspot-crm)

Also mapped by other connectors `identity.user` **517** `crm.company` **227** `crm.contact` **192** `device.endpoint` **69** `monitoring.alert` **56**

ask

```
ask {
  intent: "which Domotz companies have invoices in NetSuite, and how many each",
  steps: [
    { action: "domotz.organizations.list", as: "co", input: {}, limit: 100, max_pages: 5 },
    { action: "netsuite.views.invoices", as: "inv", input: {}, limit: 100, max_pages: 5 },
    { join: {
        left: "co",
        right: "inv",
        on: "crm.company",
        group_by: "co.name",
        select: ["co.name", "count(inv.id) as invoices"]
    } }
  ]
}
```

Example. Run it through check first: it validates the steps and prices them, and it is free.

Governance for Domotz

## Destructive actions wait for a yes.

32 Domotz actions are destructive. The first 10:

- User deletion `domotz.members.delete`
- Delete Organization Contact `domotz.organization_contacts.delete`
- Delete Organization `domotz.organizations.delete`
- User group deletion `domotz.user_groups.delete`
- Device deletion `domotz.devices.delete`
- Tag deletion `domotz.custom_tags.delete`
- Hide a device `domotz.devices.hide`
- Inventory deletion `domotz.inventory.delete`
- Collector deletion `domotz.collectors.delete`
- Bulk offline devices deletion `domotz.down_devices.delete`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do domotz.members.delete confirm_policy: **human**

User deletion?

**intent:** the user asked me to user deletion

run suspended · waiting for a named person · key _domotz-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "domotz-agent",
  allowed_actions: ["domotz.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "domotz.members.delete", approver: "lead@example.com" },
    { match: "domotz.organization_contacts.delete", approver: "lead@example.com" },
    { match: "domotz.organizations.delete", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Domotz only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What Domotz costs on actionlake.

Every Domotz action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Domotz refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 176 Domotz actions
- 176 actions page each page of a long list is one call
- 87 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Domotz action.

176 actions by area: the id your agent calls, what it does, and its effect.

**Custom driver associations 5**

- `domotz.custom_driver_associations.create` Driver device binding write
- `domotz.custom_driver_associations.delete` Driver device unbinding destructive
- `domotz.custom_driver_associations.list` Driver device bindings list read
- `domotz.custom_driver_associations.re_enable` Disabled Drivers reactivation write
- `domotz.custom_driver_associations.update` Driver device binding paramaters update write

**Devices 5**

- `domotz.devices.delete` Device deletion destructive
- `domotz.devices.get` Device details read
- `domotz.devices.hide` Hide a device destructive
- `domotz.devices.list` Collector devices list read
- `domotz.devices.update_field` Device property change write

**Members 5**

- `domotz.members.create` User creation write
- `domotz.members.delete` User deletion destructive
- `domotz.members.get` User read
- `domotz.members.list` User list read
- `domotz.members.update` User edit write

**Organization contacts 5**

- `domotz.organization_contacts.create` Create Organization Contact write
- `domotz.organization_contacts.delete` Delete Organization Contact destructive
- `domotz.organization_contacts.get` Get Organization Contact Details read
- `domotz.organization_contacts.list` List Organization Contacts read
- `domotz.organization_contacts.update` Update Organization Contact write

**Organizations 5**

- `domotz.organizations.create` Create Organization write
- `domotz.organizations.delete` Delete Organization destructive
- `domotz.organizations.get` Get Organization Details read
- `domotz.organizations.list` List Organizations read
- `domotz.organizations.update` Update Organization write

**User groups 5**

- `domotz.user_groups.create` User group creation write
- `domotz.user_groups.delete` User group deletion destructive
- `domotz.user_groups.get` User group read
- `domotz.user_groups.list` User group list read
- `domotz.user_groups.update` User group edit write

**Alert rules 4**

- `domotz.alert_rules.create` Create Alert Rule write
- `domotz.alert_rules.get` Get Alert Rule Details read
- `domotz.alert_rules.list` List Alert Rules read
- `domotz.alert_rules.update` Update Alert Rule write

**Custom tags 4**

- `domotz.custom_tags.create` Tag creation write
- `domotz.custom_tags.delete` Tag deletion destructive
- `domotz.custom_tags.list` Tag list read
- `domotz.custom_tags.update` Tag edit write

**Alert profile collector bindings 3**

- `domotz.alert_profile_collector_bindings.create` Alert profile collector binding write
- `domotz.alert_profile_collector_bindings.delete` Alert profile collector unbinding destructive
- `domotz.alert_profile_collector_bindings.get` Collector alert profile bindings read

**Alert profile device bindings 3**

- `domotz.alert_profile_device_bindings.create` Alert profile device binding write
- `domotz.alert_profile_device_bindings.delete` Alert profile device unbinding destructive
- `domotz.alert_profile_device_bindings.list` Device alert profile bindings read

**Collector custom tag bindings 3**

- `domotz.collector_custom_tag_bindings.create` Collector Tag assignment write
- `domotz.collector_custom_tag_bindings.delete` Collector Tag removal destructive
- `domotz.collector_custom_tag_bindings.list` Collector Tag list read

**Collector excluded devices 3**

- `domotz.collector_excluded_devices.create` Device exclusion write
- `domotz.collector_excluded_devices.delete` Device exclusion removal destructive
- `domotz.collector_excluded_devices.list` Excluded devices list read

**Collector external host scan policy 3**

- `domotz.collector_external_host_scan_policy.delete` External host scan policy reset destructive
- `domotz.collector_external_host_scan_policy.get` External host scan policy read
- `domotz.collector_external_host_scan_policy.update` External host scan policy update write

**Collector interfaces policy 3**

- `domotz.collector_interfaces_policy.delete` Network interface policy reset destructive
- `domotz.collector_interfaces_policy.get` Network interface filtering policy read
- `domotz.collector_interfaces_policy.update` Network interface filtering policy update write

**Collector ip scan policy 3**

- `domotz.collector_ip_scan_policy.delete` IP address scan policy reset destructive
- `domotz.collector_ip_scan_policy.get` IP address scan policy read
- `domotz.collector_ip_scan_policy.update` IP address scan policy update write

**Collector service ports 3**

- `domotz.collector_service_ports.delete` Service port removal destructive
- `domotz.collector_service_ports.get` Service port read
- `domotz.collector_service_ports.update` Service port update write

**Collector VPN sessions 3**

- `domotz.collector_vpn_sessions.create` VPN connection creation write
- `domotz.collector_vpn_sessions.delete` Active VPN connection closure destructive
- `domotz.collector_vpn_sessions.list` Active VPN connections list read

**Collectors 3**

- `domotz.collectors.delete` Collector deletion destructive
- `domotz.collectors.get` Collector details read
- `domotz.collectors.list` List collectors read

**Device configurations 3**

- `domotz.device_configurations.create` Device configuration creation write
- `domotz.device_configurations.get` Device configuration detail read
- `domotz.device_configurations.list` Device configurations list read

**Device custom tag bindings 3**

- `domotz.device_custom_tag_bindings.create` Device Tag assignment write
- `domotz.device_custom_tag_bindings.delete` Device Tag removal destructive
- `domotz.device_custom_tag_bindings.list` Device Tag list read

**Device power outlets 3**

- `domotz.device_power_outlets.execute_action` Power outlet action operation write
- `domotz.device_power_outlets.list` Device power outlets list read
- `domotz.device_power_outlets.update` Power outlet name update write

**Device SNMP sensors 3**

- `domotz.device_snmp_sensors.create` SNMP sensor creation write
- `domotz.device_snmp_sensors.delete` SNMP sensor deletion destructive
- `domotz.device_snmp_sensors.list` SNMP sensors list read

**Device TCP sensors 3**

- `domotz.device_tcp_sensors.create` TCP sensor creation write
- `domotz.device_tcp_sensors.delete` TCP sensor deletion destructive
- `domotz.device_tcp_sensors.list` TCP sensors list read

**Inventory fields 3**

- `domotz.inventory_fields.create` Inventory field creation write
- `domotz.inventory_fields.delete` Inventory field deletion destructive
- `domotz.inventory_fields.update` Inventory field update write

**SNMP sensor triggers 3**

- `domotz.snmp_sensor_triggers.create` SNMP sensor trigger creation write
- `domotz.snmp_sensor_triggers.delete` SNMP sensor trigger deletion destructive
- `domotz.snmp_sensor_triggers.list` SNMP sensor triggers list read

**Alert rule collector bindings 2**

- `domotz.alert_rule_collector_bindings.create` Apply Alert Rule to Collector write
- `domotz.alert_rule_collector_bindings.delete` Remove Alert Rule from Collector destructive

**Alert rule contact channel bindings 2**

- `domotz.alert_rule_contact_channel_bindings.create` Apply Contact Channel to Alert Rule write
- `domotz.alert_rule_contact_channel_bindings.delete` Remove Contact Channel from Alert Rule destructive

**Alert rule device bindings 2**

- `domotz.alert_rule_device_bindings.create` Apply Alert Rule to Device write
- `domotz.alert_rule_device_bindings.delete` Remove Alert Rule from Device destructive

**Alerts 2**

- `domotz.alerts.list` List Alerts read
- `domotz.alerts.resolve` Resolve Alert write

**Collector SNMP authentication 2**

- `domotz.collector_snmp_authentication.get` Collector default SNMP authentication read
- `domotz.collector_snmp_authentication.update` Collector default SNMP authentication update write

**Collector uptimes 2**

- `domotz.collector_uptimes.get` Collector uptime read
- `domotz.collector_uptimes.list` All collectors uptime read

**Custom drivers 2**

- `domotz.custom_drivers.get` Driver details read
- `domotz.custom_drivers.list` Drivers list read

**Device inventory fields 2**

- `domotz.device_inventory_fields.delete` Device inventory field deletion destructive
- `domotz.device_inventory_fields.update` Device inventory field update write

**Device power actions 2**

- `domotz.device_power_actions.execute` Device power action operation write
- `domotz.device_power_actions.list` Device power management actions read

**Device profiles 2**

- `domotz.device_profiles.apply` Device profile application write
- `domotz.device_profiles.list` Device profiles list read

**Device SNMP authentication 2**

- `domotz.device_snmp_authentication.get` Device SNMP authentication details read
- `domotz.device_snmp_authentication.update` Device SNMP authentication update write

**Inventory 2**

- `domotz.inventory.delete` Inventory deletion destructive
- `domotz.inventory.get` Inventory fields list read

**Organization collector bindings 2**

- `domotz.organization_collector_bindings.create` Apply Organization to Collector write
- `domotz.organization_collector_bindings.delete` Remove Organization from Collector destructive

**Power outlet attachments 2**

- `domotz.power_outlet_attachments.create` Power outlet device attachment write
- `domotz.power_outlet_attachments.delete` Power outlet device detachment destructive

**Roles 2**

- `domotz.roles.get` Role read
- `domotz.roles.list` Role list read

**SNMP sensor trigger alerts 2**

- `domotz.snmp_sensor_trigger_alerts.create` SNMP sensor trigger alert creation write
- `domotz.snmp_sensor_trigger_alerts.delete` SNMP sensor trigger alert deletion destructive

**Teams 2**

- `domotz.teams.create` Create a new Team write
- `domotz.teams.list` Return all the teams of an Area read

**Alert profiles 1**

- `domotz.alert_profiles.list` Alert profiles list read

**API usage 1**

- `domotz.api_usage.get` API usage and limits read

**Areas 1**

- `domotz.areas.list` Company areas list read

**Audit logs 1**

- `domotz.audit_logs.list` List Audit Logs read

**Collector activity logs 1**

- `domotz.collector_activity_logs.list` Activity log read

**Collector alert rules 1**

- `domotz.collector_alert_rules.list` List Alert Rules applied to a Collector read

**Collector connection consumption 1**

- `domotz.collector_connection_consumption.get` Remote connections consumption read

**Collector custom driver execution logs 1**

- `domotz.collector_custom_driver_execution_logs.list` Collector drivers execution logs read

**Collector datapoints 1**

- `domotz.collector_datapoints.list` List Collector Entity Datapoints read

**Collector device applications 1**

- `domotz.collector_device_applications.list` Collector device applications list read

**Collector device variables 1**

- `domotz.collector_device_variables.list` Collector device variables list read

**Collector DHCP device discovery 1**

- `domotz.collector_dhcp_device_discovery.update` DHCP device discovery setting write

**Collector eye statistics 1**

- `domotz.collector_eye_statistics.get` Sensors usage and limits read

**Collector interfaces 1**

- `domotz.collector_interfaces.get` Monitored networks read

**Collector ip conflicts 1**

- `domotz.collector_ip_conflicts.list` Active IP conflicts read

**Collector metric statistics 1**

- `domotz.collector_metric_statistics.get` Metrics usage and limits read

**Collector network topology 1**

- `domotz.collector_network_topology.get` Network topology read

**Collector ownership 1**

- `domotz.collector_ownership.update` Collector team reassignment write

**Collector routed networks 1**

- `domotz.collector_routed_networks.create` Routed network creation write

**Collector RTD stats 1**

- `domotz.collector_rtd_stats.list` Round Trip Delay statistics read

**Collector SNMP sensors 1**

- `domotz.collector_snmp_sensors.list` Collector SNMP sensors list read

**Collector speed tests 1**

- `domotz.collector_speed_tests.list` Internet Speed Test time series read

**Collector status history 1**

- `domotz.collector_status_history.list` Collector state change history read

**Collector TCP sensors 1**

- `domotz.collector_tcp_sensors.list` Collector TCP sensors list read

**Collector variable history 1**

- `domotz.collector_variable_history.list` Collector variable history read

**Collector variables 1**

- `domotz.collector_variables.list` Collector variables list read

**Contact channels 1**

- `domotz.contact_channels.list` List Contact Channels read

**Current user 1**

- `domotz.current_user.get` Account details read

**Custom driver actions 1**

- `domotz.custom_driver_actions.execute` Driver action trigger write

**Datapoints 1**

- `domotz.datapoints.get` Datapoint details read

**Device alert rules 1**

- `domotz.device_alert_rules.list` List Alert Rules applied to a Device read

**Device applications 1**

- `domotz.device_applications.list` Device applications list read

**Device base types 1**

- `domotz.device_base_types.list` Device types list read

**Device configuration backups 1**

- `domotz.device_configuration_backups.create` Device configuration backup execution write

**Device connections 1**

- `domotz.device_connections.create` Device secure connection creation write

**Device credentials 1**

- `domotz.device_credentials.update` Device credentials update write

**Device custom driver execution logs 1**

- `domotz.device_custom_driver_execution_logs.list` Device drivers execution logs read

**Device datapoints 1**

- `domotz.device_datapoints.list` List Device Entity Datapoints read

**Device detected types 1**

- `domotz.device_detected_types.list` Detected device types list read

**Device inventory 1**

- `domotz.device_inventory.get` Device inventory fields list read

**Device monitoring state 1**

- `domotz.device_monitoring_state.update` Device monitoring state update write

**Device RTD history 1**

- `domotz.device_rtd_history.list` Round Trip Delay statistics history read

**Device SNMP community 1**

- `domotz.device_snmp_community.update` Device SNMP community update write

**Device status history 1**

- `domotz.device_status_history.list` Device state change history read

**Device uptimes 1**

- `domotz.device_uptimes.get` Device uptime read

**Device variable history 1**

- `domotz.device_variable_history.list` Device variable history read

**Device variables 1**

- `domotz.device_variables.list` Device variables list read

**Down devices 1**

- `domotz.down_devices.delete` Bulk offline devices deletion destructive

**External hosts 1**

- `domotz.external_hosts.create` External host creation write

**SNMP sensor history 1**

- `domotz.snmp_sensor_history.list` SNMP sensor time series read

**SNMP sensor trigger functions 1**

- `domotz.snmp_sensor_trigger_functions.list` SNMP sensor trigger functions list read

**Unmanaged devices 1**

- `domotz.unmanaged_devices.list` Unmanaged devices list read

**User alert profiles 1**

- `domotz.user_alert_profiles.list` Alert profiles list read

Questions

## The Domotz MCP server, answered.

**Is there a Domotz MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 176 Domotz actions across custom driver associations, devices, members and organization contacts, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Domotz.

**What do I need to connect Domotz?**

Domotz API key: in the Domotz Portal open Settings > Services > API Keys and create a key. Plus your host. The free call account { op: "connections.requirements", service: "domotz" } lists exactly what to paste.

**Can an AI agent delete or change things in Domotz?**

Only if its key allows it, and only with an explicit confirmation. 32 Domotz actions are destructive, including user deletion, delete Organization Contact and delete Organization. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my Domotz API limit?**

actionlake paces every call to the limits in the Domotz service file: 10 calls a second per connection. Repeated reads are answered from cache (87 Domotz actions can be), which never reaches Domotz.

**What does a Domotz action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (176 Domotz actions page). Cache hits, searches, dry runs and calls Domotz refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which Domotz API does it cover?**

The Domotz Public API 1 (OpenAPI 3.1) at your Domotz instance's API base URL, which you enter when connecting (path /public-api/v1). It is built from Domotz's documentation as read on 23 October 2026. 176 actions in 95 areas, each one in the signed service file (version 1.0.0).

**Can I combine Domotz with my other systems?**

Yes. ask joins Domotz to NetSuite or HubSpot CRM on the same customer and returns the answer rather than every row. Domotz maps crm.company, which 227 other connectors also map.

**Does actionlake keep my Domotz data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Domotz credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like Domotz

Shares the most action names with

- [Kaseya VSA 17](https://actionlake.com/connectors/kaseya-vsa)
- [3CX 15](https://actionlake.com/connectors/3cx)
- [Veeam Service Provider Console 14](https://actionlake.com/connectors/veeam-service-provider-console)
- [Cato Networks SASE 12](https://actionlake.com/connectors/cato-networks-sase)
- [ThreatDown OneView 12](https://actionlake.com/connectors/threatdown-oneview)
- [MSP360 Managed Backup 12](https://actionlake.com/connectors/msp360-managed-backup)

Joins with, on shared entities

- [Microsoft 365 Users 3](https://actionlake.com/connectors/microsoft-365-users)
- [Salesforce Sales Cloud 3](https://actionlake.com/connectors/salesforce-sales-cloud)
- [Genesys Cloud CX 3](https://actionlake.com/connectors/genesys-cloud-cx)
- [Bitrix24 3](https://actionlake.com/connectors/bitrix24)
- [Odoo 3](https://actionlake.com/connectors/odoo)
- [Zoho Desk 3](https://actionlake.com/connectors/zoho-desk)

Browse

- [All MSP & PSA connectors](https://actionlake.com/connectors/category/msp-and-psa)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Domotz; the name is the vendor's own. Counts are from the Domotz service file, version 1.0.0.

## Give your agent Domotz today.

[Connect Domotz free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/domotz
More: https://actionlake.com/llms.txt