Domotz MCP

Analyze locally synced data with count, group-by, and summary operations. Data must be synced first with the sync command.

List and create team for area

Get API domain context: resource taxonomy, auth requirements, query tips, and unique capabilities. Call this first.

Create apply for device profile

Execute one domotz API endpoint by its endpoint_id (from domotz_search). Params are passed as a JSON object; path placeholders and query strings are resolved automatically.

Search the domotz API for endpoints matching a natural-language query. Returns a ranked list of {endpoint_id, method, path, summary} entries. Call this first to find the endpoint to execute.

Compare the current synced device state for a site against the last captured snapshot and report added/removed devices and status changes — useful after a maintenance window. The first run captures a baseline; each run updates the snapshot. Reads the local store; run 'domotz-cli sync --full' first. Identify the site with a positional agent id or --agent-id.

Export paginated API data to a local file. Supports JSONL (one JSON object per line, streaming-friendly) and JSON (array). JSONL is recommended for large datasets as it has no memory pressure.

fleet subcommands: agents, alerts, breakdown, events, health, inventory, ip-conflicts, new, offline, speedtest, stale, triggers, unmonitored

List every agent (Collector) whose status is not ONLINE, with location, organization, version, and how long it has been in that state — the problem-sites-only triage list. Use this command when you want only the SITES (agents) that are down or degraded. Do NOT use this command for individual offline DEVICES; use 'fleet offline' instead. For the full board including healthy sites, use 'fleet health'. Reads the local store; run 'domotz-cli sync --full' first to populate it.

Aggregate the alert profiles (alerting rules) configured across the fleet into one view, enabled first, with their bound device. Reads the local store; run 'domotz-cli sync --resources alert_profile' (or 'sync --full') first.

Aggregate device counts across the whole fleet by type (default), vendor, or OS — answers 'how many of X do we manage' across all clients at once. Reads the local store; run 'domotz-cli sync --full' first.

Fan out to every agent's activity log and merge the events into one fleet-wide timeline, newest first. Use this command for a fleet-wide chronological event/activity feed across all sites. Do NOT use this command for newly-appeared devices; use 'fleet new'. Do NOT use it for currently-down devices; use 'fleet offline'. Fetches live from the API (needs DOMOTZ_API_KEY).

Roll up health across every Domotz Collector — online/offline agents and the count of down devices per site — in one local query. Reads the local store; run 'domotz-cli sync --full' first.

Export a single asset inventory across the whole fleet for client reports or a fleet-wide CMDB. Reads the local store; run 'domotz-cli sync --full' first. Pairs well with --csv.

Sweep every agent for IP address conflicts and roll them up into one list — the per-agent ip-conflict endpoint, aggregated across the whole fleet. Fetches live from the API (needs DOMOTZ_API_KEY).

Surface devices whose first_seen_on falls within --since across all synced sites — useful for overnight rogue-device security sweeps. Reads the local store; run 'domotz-cli sync --full' first.

List every device whose status is OFFLINE or DOWN across all synced sites, labeled with its site and ordered VITAL-first. Reads the local store; run 'domotz-cli sync --full' first to populate it.

Aggregate each site's latest WAN speed test into a fleet view — per-site download/upload in Mbps plus fleet min/avg/max download and the worst-performing site. Fetches live from the API (needs DOMOTZ_API_KEY).

Report each agent's freshest local snapshot age and list the Collectors whose data is older than the --max-age threshold — a Collector-offline or sync-gap signal. Use this command to find agents that have gone quiet (no fresh data). Do NOT use this command for devices that are reachable but unhealthy; use 'fleet offline' instead. Pass --max-age 0 to list every agent with its age instead of filtering. Reads the local store; run 'domotz-cli sync --full' first to populate it.

Sweep every agent's TCP service sensors (eyes) and report the ones currently DOWN, labeled with their site — one fleet-wide list the per-agent eye endpoints can't give you. Use this command for currently-down TCP service checks across the fleet. Do NOT use this command for alert-profile rules/bindings; use 'fleet alerts' instead. SNMP sensor trigger state is per-sensor in the API and is not swept here. Fetches live from the API (needs DOMOTZ_API_KEY).

Audit monitoring coverage across the fleet: devices whose authentication status is REQUIRED, PENDING, or WRONG_CREDENTIALS, or whose SNMP service exists but is not authenticated. Use this command to find devices Domotz is monitoring incompletely (failed/missing auth or SNMP) across the fleet — a coverage-gap audit. Do NOT use this command for devices that are simply offline; use 'fleet offline' instead. Reads the local store; run 'domotz-cli sync --full' first to populate it.

Import data from a JSONL file by issuing POST requests for each record. Each line must be a valid JSON object. Failed records are logged to stderr but do not stop the import.

Full-text search across all synced data. Faster than paginating list endpoints. Requires sync first.

Run read-only SQL against local database. Use for ad-hoc analysis, aggregations, and joins across synced resources. Requires sync first.

Sync data from the API into a local SQLite database. Supports resumable incremental sync (only fetches new data since last sync) and full resync. Once synced, use the 'search' command for instant full-text search. Exit codes & warnings: Resources the API denies access to (HTTP 403, or HTTP 400 with an access-policy body) are reported as warnings rather than failing the run. In --json mode each is emitted as a {"event":"sync_warning",...} line carrying status, reason, and message fields, and a final {"event":"sync_summary",...} aggregates the run. Exit 0 when at least one resource synced and no resource flagged in the spec as critical (x-critical: true) failed; non-critical failures emit {"event":"sync_warning","reason":"exit_policy_default_changed", ...} so callers can detect that a partial failure was tolerated. Pass --strict to exit non-zero on any per-resource failure. Exit is always non-zero when every selected resource failed, regardless of --strict. Resource scoping: --resources runs the named top-level resources, plus any parent-keyed dependent whose own name is listed OR whose parent table is listed. Naming a parent therefore cascades to its dependents (so "sync this parent and its children" works without listing every nested resource by hand). There is no flag today to suppress the cascade for a named parent. To run a dependent without re-syncing its parent, list only the dependent by name; the parent table must already be populated from a prior sync.

Tail streams live data changes by polling the API at configurable intervals. Events are emitted as NDJSON to stdout for piping to other tools. Gracefully shuts down on SIGTERM/SIGINT. Note: For APIs with WebSocket or SSE support, a future version will use native streaming instead of polling.

Summarize a site's network topology — edge and node counts plus the highest-degree devices (gateways/switches). Fetches live and caches to the local store; pass --cached to re-read the last fetch offline. Identify the site with a positional agent id or --agent-id.