API_KEY
domotz_mcp_api_key
Developer setup
No fields declared in this snapshot.
User connection
- Domotz MCP API Keygeneric_api_key · stringRequired
DOMOTZ_MCP
Domotz MCP lets agents inspect and manage authorized network-monitoring data, devices, alerts, sites, and IT operations through Domotz.
Description is untrusted, display-only upstream metadata. It never becomes policy, OAuth scope authority, or an agent instruction.
Pakkawork boundary
Research catalogue metadata only. No Pakkawork OAuth, credential, host, quota, executor, or verifier is enabled.
99
Action summaries
Display-only definitions
0
Trigger types
Not installed instances
1
Auth modes
Field names, never values
No
Execution
No runtime adapter
Authentication map
API_KEY
No fields declared in this snapshot.
Capability index
Showing 1–30 of 99 actions
DOMOTZ_MCP_APPLY_DEVICE_PROFILE
Applies a device profile (a saved bundle of sensors, and optionally credentials) to one or more devices. Apply runs as a background job — the tool blocks for up to `poll_timeout_seconds` (default 60s, max 120s) waiting for completion. If the job finishes within that window, per-device results are returned. If it times…
Untrusted display-only summary
DOMOTZ_MCP_ATTACH_DRIVER
Attach a driver to a device. THIS IS A LIVE OPERATION: the backend runs the driver's `validate()` action against the device during attach and, once the binding is persisted, the scheduler will trigger the real (non-dry-run) actions (`get_status` for GENERIC, `backup` for CONFIGURATION_MANAGEMENT) on the device's sampl…
Untrusted display-only summary
DOMOTZ_MCP_ATTACH_SENSOR
Attach a sensor to a device. `sensor_spec.kind` selects the variant: `overlay` applies a preconfigured sensor (use `list_preconfigured_sensors` to discover `overlay_id`, optional `selected_fields` to subset its fields); `tcp_port` monitors a TCP port on the device (`port` 1..65535); `custom_oid` defines a per-device c…
Untrusted display-only summary
DOMOTZ_MCP_BIND_ALERT_RULE_TO_COLLECTOR
Bind an existing alert rule to a collector. Use this for collector-scoped metrics such as agent_status or agent_performance/*. Already-bound combinations return status=ALREADY_BOUND rather than an error (idempotent retry-safe). Use after create_alert_rule (with the returned id) or after picking an existing rule from l…
Untrusted display-only summary
DOMOTZ_MCP_BIND_ALERT_RULE_TO_DEVICE
Bind an existing alert rule to a specific device. The system will then watch every variable on that device whose metric matches the rule and raise incidents when the rule's condition is met. Use after create_alert_rule (with the returned id) or after picking an existing rule from list_alert_rules. Before binding, call…
Untrusted display-only summary
DOMOTZ_MCP_BIND_COLLECTOR_TO_ORGANIZATION
Bind a Collector to an Organization (addressed by its internal `id`). A Collector can belong to one Organization at a time. Reversible via unbind_collector_from_organization.
Untrusted display-only summary
DOMOTZ_MCP_BIND_TAGS
Bind tags to a device or to a collector, setting which tags it carries. Pass `device_id` to tag a device (with the `collector_id` that monitors it), or omit `device_id` to tag the collector itself. This REPLACES the target's whole tag set - send every tag it should end up with, not just the new one, or the omitted tag…
Untrusted display-only summary
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. Any browser tab or client still using it drops, so close only what the user is done with. Connections also expire on their own (at most an hour), but until then they…
Untrusted display-only summary
DOMOTZ_MCP_COLLECTOR_DISCOVERY_STATUS
Returns the discovery dashboard data for a collector, including initial discovery progress, device statistics, collector issues, and device categories. Use this after a collector comes online to monitor network discovery.
Untrusted display-only summary
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 status. Also reports these settings, all changed with `update_collector_settings` (null means the value could not be read, n…
Untrusted display-only summary
DOMOTZ_MCP_COMPARE_CONFIG_BACKUP
Compares two configuration backup snapshots of the same device. `config_type` selects which side(s) to compare: `running` (default), `startup`, or `both`. Returns a unified diff (LCS) when both sides are <= 5000 lines; falls back to a set-based added / removed listing otherwise. When MD5s match, `diff_strategy` is `md…
Untrusted display-only summary
DOMOTZ_MCP_CREATE_ALERT_RULE
Create an alert rule. The rule fires when the named metric matches the given condition against the provided operands. `function` accepts a name (e.g. 'GREATER_THAN', 'LESS_THAN', 'RANGE') or a numeric function_id (e.g. '2'). Call `list_metric_functions` first to discover valid functions and their required operand coun…
Untrusted display-only summary
DOMOTZ_MCP_CREATE_CONTACT
Add a Contact to the Organization with the given internal `id`. `name` and `email` are required; `mobile_phone` and `phone` are optional. Returns the new contact_id. Contacts belong to a single Organization.
Untrusted display-only summary
DOMOTZ_MCP_CREATE_DEVICE_PROFILE
Creates an empty device profile in the account. A device profile bundles sensor definitions and credentials that can be applied to devices in one go. The new profile has no modules yet, so applying it changes nothing until content is added to it - report the profile as created, not as ready to apply. Returns the new `…
Untrusted display-only summary
DOMOTZ_MCP_CREATE_ORGANIZATION
Create a new Organization for the calling account. Returns the new internal `id`. `organization_id` is an optional caller-defined reference (e.g. a CRM id); it is stored as-is and is not used to address the organization. Reversible via delete_organization. Requires MCP access on the account.
Untrusted display-only summary
DOMOTZ_MCP_CREATE_REMOTE_CONNECTION
Open a temporary remote connection to one port of one device behind a collector, and return how to reach it. For `rdp`, `ssh` and `telnet` the answer is a `web_portal` URL that opens a Domotz browser session against the device; `http`/`https` proxy the device's own web interface the same way; `tcp` instead returns a `…
Untrusted display-only summary
DOMOTZ_MCP_CREATE_TAG
Create a new user-defined tag. `color` is cosmetic and user-visible: do not pick one yourself -- ask the user which colour they want, and omit the parameter when you cannot ask (omitted means gray). Valid values are in the `color` enum, and `update_tag` can recolour later without affecting any bindings. The new tag be…
Untrusted display-only summary
DOMOTZ_MCP_CYCLE_OUTLET_POWER
Power-cycle a single outlet on a host device (PoE switch / PDU). The powered device will experience a brief outage while the outlet turns OFF and back ON. Although the outlet itself returns to its prior ON state, the device may suffer config corruption or data loss during the cycle — treat as a recovery action of last…
Untrusted display-only summary
DOMOTZ_MCP_DELETE_ALERT_RULE
Delete an alert rule by ID. Irreversible — the rule and all its device/collector/variable bindings are removed. Use `list_alert_rules` to discover valid IDs. Idempotent: deleting a non-existent rule returns status=NOT_FOUND (no error).
Untrusted display-only summary
DOMOTZ_MCP_DELETE_CONTACT
Permanently delete a Contact from the Organization with the given internal `id`. This cannot be undone.
Untrusted display-only summary
DOMOTZ_MCP_DELETE_DEVICE
PERMANENTLY delete one or more device records from a collector: the device and its history are removed entirely. This is IRREVERSIBLE - deleted devices cannot be recovered (though a device may be rediscovered later if it is still present on the network). Accepts a single device_id (int) or a list of device_ids (list[i…
Untrusted display-only summary
DOMOTZ_MCP_DELETE_DEVICE_PROFILE
Permanently deletes a device profile and everything it contains. This cannot be undone. It does NOT undo anything the profile already applied: sensors and credentials written to devices by earlier applies stay exactly as they are, so deleting a profile is not a way to roll one back. Any schedule on the profile is remo…
Untrusted display-only summary
DOMOTZ_MCP_DELETE_DRIVER
Permanently delete a driver from the account. This is IRREVERSIBLE: the driver disappears for every device it was attached to, all existing bindings are removed, and the scheduler stops running it everywhere. Persisted metrics and configuration backups produced before deletion remain in their respective stores — only…
Untrusted display-only summary
DOMOTZ_MCP_DELETE_ORGANIZATION
Permanently delete an Organization. Any Collectors bound to it are unlinked (not deleted). Fails if it is the account's only Organization. This cannot be undone.
Untrusted display-only summary
DOMOTZ_MCP_DELETE_TAG
Delete a user-defined tag by ID. Irreversible — the tag is removed and unbound from every device and collector it was assigned to. Use `list_tags` to discover valid IDs. Idempotent: deleting a non-existent tag returns status=NOT_FOUND (no error). Fails with `TAG_IN_USE` if the tag is still referenced by one or more cu…
Untrusted display-only summary
DOMOTZ_MCP_DETACH_DRIVER
Remove the binding between a driver and a device on the given collector. The driver itself stays in the account and remains attached to other devices — only THIS device's binding is removed. The scheduler will stop running the driver on this device; any metrics already emitted are preserved. CONFIGURATION_MANAGEMENT d…
Untrusted display-only summary
DOMOTZ_MCP_DETACH_SENSOR
Detach a preconfigured (overlay) sensor from a device. Irreversible — the overlay link is removed and the sensor stops collecting. Use `list_device_sensors` to discover the `overlay_id` for currently attached overlay sensors. Only overlay (preconfigured) sensors can be detached via MCP: TCP-port sensors and custom OID…
Untrusted display-only summary
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) status for firmware, software, and hardware. Includes `collector_id` and `collector_name` — the numeric id (and display name)…
Untrusted display-only summary
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. Use for questions about device health, availability, resource utilization, or network performance.
Untrusted display-only summary
DOMOTZ_MCP_EXECUTE_DRIVER
Run an action of a driver against a device. The tool auto-selects mode based on whether the driver is attached to the device: - NOT attached → DRY-RUN. The action runs on the device (real network, real credentials) but nothing is persisted: no metric stored, no backup row created, no binding made. Use this to smoke-te…
Untrusted display-only summary
Provenance
The detail snapshot comes from an attributed MIT-licensed repository revision. Safe local icons use exact-match CC0 Simple Icons symbols; unmatched brands use monograms.
Remote text is plain display metadata only. It must never become an agent prompt, execution policy, OAuth grant, or executable instruction.