Domotz MCP
for LuumenAI
Read Domotz sites, devices, and alerts, then make the change as an approved step
Connect Domotz and Luumen can answer questions about your monitored networks without you opening the console: collector health, device inventory, performance history, config backup status, and which alert rules are bound where. When something needs to change, the agent proposes the exact call and waits for your approval before it runs. Access uses an API key.
The Domotz MCP toolbox
99 tools: 48 read, 51 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadCollector discovery statusReturns the discovery dashboard data for a collector, including initial discovery progress, device statistics, collector issues, and device categories.
- ReadCollector overviewFetch 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…
- ReadCompare config backupCompares two configuration backup snapshots of the same device.
- ReadDevice inventoryReturns 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)…
- ReadDevice performanceFetch device performance metrics including round-trip delay, packet loss, uptime, SNMP sensor values, and disk usage over the last 7 days.
- ReadGet account infoReturns 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.
- ReadGet audit log filtersReturn 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…
- ReadGet collector alert rule bindingsList alert rules bound to a specific collector, including bindings at the collector level and bindings to variables owned by that collector.
- ReadGet collector capabilitiesInspect what the customer's Collector can actually run.
- ReadGet collector credential coverageCollector-wide credential audit.
- ReadGet config backup entryReturns a single configuration backup snapshot's text for a device.
- ReadGet config backup statusLists 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)…
- ReadGet device alert rule bindingsList alert rules bound to a specific device, including device-level bindings and bindings to variables owned by that device.
- ReadGet device alertsRetrieve alert and monitoring configuration status for a specific device.
- ReadGet device credentialsPer-device credential status drill-down.
- ReadGet device historyReturns the per-device History / Event Log for a single device: the chronological stream of events the device generated, most recent first.
- ReadGet device interfacesLists the SNMP-collected interfaces on a device.
- ReadGet device metricsFetch summarised time-series analytics for one or more named metrics on a device within a time range.
- ReadGet device profile job historyLists device-profile apply jobs for the account: which profile was applied, who submitted it, when it started and ended, how it finished, and which devices failed.
- ReadGet driver catalogLists the account-wide catalog of drivers available for attaching and executing on devices.
- ReadGet driver templateFetch a single driver template, including its full JS code body and requirement metadata (`requirements.sandbox_version`, etc.).
- ReadGet interface trafficReturns traffic counters for one or more device interfaces over a time range.
- ReadGet network configurationFetch what a collector actually scans, to answer 'why isn't this device discovered?'.
- ReadGet organizationGet 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.
- ReadGet uptimeReturns uptime stats for a collector or device over a time range: total uptime percentage, online_seconds, total_seconds, and the list of downtime intervals.
- ReadInspect driverStatic analysis of a driver's JS against the Domotz sandbox.
- ReadList alert rulesLists alert rule definitions in the account.
- ReadList collector metricsEnumerate 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.
- ReadList communication channelsList the user's notification channels (email, webhook, Slack, etc.).
- ReadList config backup historyLists configuration backup snapshots for a device on a collector, newest first.
- ReadList device driversLists drivers currently attached to a device.
- ReadList device metricsList everything monitorable on a device.
- ReadList device profilesLists device profiles in the account.
- ReadList device sensorsLists the sensors currently attached to a device, merged across CUSTOM_OID, TCP, CUSTOM_DRIVER, and PRECONFIGURED kinds.
- ReadList device typesReturns the device-type catalog used to classify devices (router, switch, AP, server, etc.).
- ReadList driver templatesList shared driver templates the account can start from.
- ReadList metric functionsList the evaluation functions (e.g.
- ReadList organizationsList the account's Organizations with their Contacts and bound Collector ids.
- ReadList preconfigured sensorsReturns the account-wide catalog of preconfigured sensors available to attach via `attach_sensor(sensor_spec={kind: 'overlay', overlay_id: ...})`.
- ReadList remote connectionsList the remote connections of a collector - by default the ones still open, with the device and port each reaches and how long before it expires.
- ReadList tagsReturns the account-wide catalog of user-defined tags applied to devices and collectors.
- ReadList variable alert rule candidatesList alert rules that could be bound to a specific device variable.
- ReadNetwork topologyReturns the network topology discovered by a single collector: device-to-device links and per-outlet (port) details.
- ReadSearch alertsSearch alert history with filters.
- ReadSearch audit logsSearch Domotz audit logs for the caller's organization.
- ReadSearch collectorsSearch and list Domotz collectors with filtering and pagination (zero-based: first page is page=0).
- ReadSearch devicesCross-account device search with filters and pagination (zero-based: first page is page=0).
- ReadSearch organizationsList and filter the organizations visible to the calling user.
- WriteApply device profileApplies a device profile (a saved bundle of sensors, and optionally credentials) to one or more devices. Approval by default
- WriteAttach driverAttach a driver to a device. Approval by default
- WriteAttach sensorAttach a sensor to a device. Approval by default
- WriteBind alert rule to collectorBind an existing alert rule to a collector. Approval by default
- WriteBind alert rule to deviceBind an existing alert rule to a specific device. Approval by default
- WriteBind collector to organizationBind a Collector to an Organization (addressed by its internal `id`). Approval by default
- WriteBind tagsBind tags to a device or to a collector, setting which tags it carries. Approval by default
- WriteClose remote connectionClose a remote connection opened with `create_remote_connection`, invalidating its URL and releasing the collector's remote-access allowance immediately. Approval by default
- WriteCreate alert ruleCreate an alert rule. Approval by default
- WriteCreate contactAdd a Contact to the Organization with the given internal `id`. Approval by default
- WriteCreate device profileCreates an empty device profile in the account. Approval by default
- WriteCreate organizationCreate a new Organization for the calling account. Approval by default
- WriteCreate remote connectionOpen a temporary remote connection to one port of one device behind a collector, and return how to reach it. Approval by default
- WriteCreate tagCreate a new user-defined tag. Approval by default
- WriteCycle outlet powerPower-cycle a single outlet on a host device (PoE switch / PDU). Approval by default
- WriteDelete alert ruleDelete an alert rule by ID. Approval by default
- WriteDelete contactPermanently delete a Contact from the Organization with the given internal `id`. Approval by default
- WriteDelete devicePERMANENTLY delete one or more device records from a collector: the device and its history are removed entirely. Approval by default
- WriteDelete device profilePermanently deletes a device profile and everything it contains. Approval by default
- WriteDelete driverPermanently delete a driver from the account. Approval by default
- WriteDelete organizationPermanently delete an Organization. Approval by default
- WriteDelete tagDelete a user-defined tag by ID. Approval by default
- WriteDetach driverRemove the binding between a driver and a device on the given collector. Approval by default
- WriteDetach sensorDetach a preconfigured (overlay) sensor from a device. Approval by default
- WriteExecute driverRun an action of a driver against a device. Approval by default
- WriteGet create tag formShows an interactive form to create a new custom tag, with a name field and a color picker. Approval by default
- WriteGet snmp credentials formShows an interactive form to set or update SNMP credentials on a specific device.Only use this tool when the user explicitly asks to set, update, or change SNMP credentials for a deviceDo NOT use… Approval by default
- WriteManage external hostsAdd or remove an external host on a collector. Approval by default
- WriteManage ip scan policyManage the collector's forced IP scan policy: extra addresses the collector must probe on top of what it discovers by itself. Approval by default
- WriteManage routed networksAdd, update or remove a routed network on a collector. Approval by default
- WriteResolve alertPermanently resolve one or more alert incidents. Approval by default
- WriteSave driverCreate or update a driver on the account. Approval by default
- WriteSet collector default snmp credentialsSet the collector's DEFAULT SNMP credentials — the ones used for devices that have no SNMP credentials of their own. Approval by default
- WriteSet device credentialSet or overwrite a device credential. Approval by default
- WriteSet device powerChange the power state of a device: turn it `on`, hold it `off`, `cycle` it, or issue a `software_reboot`. Approval by default
- WriteSet interfaces policySet which of the collector's own network interfaces take part in discovery, by name. Approval by default
- WriteSnooze collector alertsSnooze (temporarily mute) all alerting for a collector for a maintenance window. Approval by default
- WriteSubmit feedbackSubmit feedback about a gap in available MCP tools or data. Approval by default
- WriteUnbind alert rule from collectorUnbind an alert rule from a collector. Approval by default
- WriteUnbind alert rule from deviceUnbind an alert rule from a device. Approval by default
- WriteUnbind collector from organizationUnbind a Collector from an Organization (addressed by its internal `id`). Approval by default
- WriteUnsnooze collector alertsResume alerting on a collector immediately, cancelling any active snooze/maintenance window set by `snooze_collector_alerts`. Approval by default
- WriteUpdate alert ruleUpdate an existing alert rule in place, preserving its device/collector/variable bindings and alert history (unlike deleting and recreating). Approval by default
- WriteUpdate collector metadataUpdate editable metadata on a collector (the on-site monitoring agent). Approval by default
- WriteUpdate collector settingsChange how a collector monitors and what it scans: the scope of its device discovery, whether the scheduled scan of the site's public IP for open TCP ports runs, the periodic ping of managed… Approval by default
- WriteUpdate contactUpdate a Contact on the Organization with the given internal `id`. Approval by default
- WriteUpdate device metadataUpdate editable metadata fields on a device: `name`, `importance` (important or not important), `zone`, `room`, `serial`, `notes` (max 256 chars). Approval by default
- WriteUpdate device monitoring stateManage or unmanage one or more devices by changing their monitoring state. Approval by default
- WriteUpdate device profileRenames or re-describes an existing device profile. Approval by default
- WriteUpdate organizationUpdate an existing Organization by its internal `id`. Approval by default
- WriteUpdate tagRename an existing user-defined tag, change its colour, or both. Approval by default
One prompt, start to finish
What a governed Domotz MCP run looks like inside Luumen.
Questions
How does LuumenAI connect to Domotz MCP?
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Can LuumenAI change things in Domotz MCP on its own?
Read actions answer immediately. Anything that writes — apply device profile, attach driver, attach sensor, bind alert rule to collector, and more — is shown as a plan and requires approval by default, including the 27 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
Who gets access to the integration?
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Is there an audit trail?
Every call to Domotz MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut Domotz MCP to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.