---
title: "Domotz MCP integration for LuumenAI"
url: "https://www.luumen.ai/integrations/domotz-mcp/"
entity: SoftwareIntegration
category: "AI & automation"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Domotz MCP integration for LuumenAI

Read Domotz sites, devices, and alerts, then make the change as an approved step

## What LuumenAI can do with Domotz MCP

LuumenAI connects to Domotz MCP with an API token and exposes 99 tools (48 read-only · 24 write · 27 destructive). For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

## Key facts

- Authentication: API token
- Tools available: 99 tools (48 read-only · 24 write · 27 destructive)
- Deployment: scoped as part of your Pilot, Platform, or Managed rollout
- Category: AI & automation

## About Domotz MCP with LuumenAI

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.

## Example tools

Read-only (48 in total):

- `DOMOTZ_MCP_COLLECTOR_DISCOVERY_STATUS` — Returns the discovery dashboard data for a collector, including initial discovery progress, device statistics, collector issues, and device categories.
- `DOMOTZ_MCP_COLLECTOR_OVERVIEW` — 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…
- `DOMOTZ_MCP_COMPARE_CONFIG_BACKUP` — Compares two configuration backup snapshots of the same device.
- `DOMOTZ_MCP_DEVICE_INVENTORY` — 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)…
- `DOMOTZ_MCP_DEVICE_PERFORMANCE` — Fetch device performance metrics including round-trip delay, packet loss, uptime, SNMP sensor values, and disk usage over the last 7 days.
- `DOMOTZ_MCP_GET_ACCOUNT_INFO` — 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.
- `DOMOTZ_MCP_GET_AUDIT_LOG_FILTERS` — 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…
- `DOMOTZ_MCP_GET_COLLECTOR_ALERT_RULE_BINDINGS` — List alert rules bound to a specific collector, including bindings at the collector level and bindings to variables owned by that collector.

Write and destructive (51 in total, subject to configured approval policy):

- `DOMOTZ_MCP_APPLY_DEVICE_PROFILE` — Applies a device profile (a saved bundle of sensors, and optionally credentials) to one or more devices.
- `DOMOTZ_MCP_ATTACH_DRIVER` — Attach a driver to a device.
- `DOMOTZ_MCP_ATTACH_SENSOR` — Attach a sensor to a device.
- `DOMOTZ_MCP_BIND_ALERT_RULE_TO_COLLECTOR` — Bind an existing alert rule to a collector.
- `DOMOTZ_MCP_BIND_ALERT_RULE_TO_DEVICE` — Bind an existing alert rule to a specific device.
- `DOMOTZ_MCP_BIND_COLLECTOR_TO_ORGANIZATION` — Bind a Collector to an Organization (addressed by its internal `id`).
- `DOMOTZ_MCP_BIND_TAGS` — Bind tags to a device or to a collector, setting which tags it carries.
- `DOMOTZ_MCP_CLOSE_REMOTE_CONNECTION` — Close a remote connection opened with `create_remote_connection`, invalidating its URL and releasing the collector's remote-access allowance immediately.

## Frequently asked 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?

For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user.

### 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.

Full page: https://www.luumen.ai/integrations/domotz-mcp/