Domotz MCP for AI Agents

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Domotz MCP or direct API to inspect devices, list active alerts, query site status, and acknowledge incidents through natural language.

Domotz MCP logoDomotz MCP
Api Key

Domotz MCP is a network-monitoring service that provides device discovery, alerts, and site telemetry. It helps IT teams monitor, troubleshoot, and manage networks remotely with clear device and alert visibility.

92 Tools

Try Domotz MCP now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
Domotz MCP
Try asking
TOOLS

Supported Tools

Every Domotz MCP action and event your agent gets out of the box.

Apply device profile

Applies a device profile (a saved bundle of sensors, and optionally credentials) to one or more devices.

Attach driver

Attach a driver to a device.

Attach sensor

Attach a sensor to a device.

Bind alert rule to collector

Bind an existing alert rule to a collector.

Bind alert rule to device

Bind an existing alert rule to a specific device.

Bind collector to organization

Bind a Collector to an Organization (addressed by its internal `id`).

Bind tags

Bind tags to a device or to a collector, setting which tags it carries.

Collector discovery status

Returns the discovery dashboard data for a collector, including initial discovery progress, device statistics, collector issues, and device categories.

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.

Compare config backup

Compares two configuration backup snapshots of the same device.

Create alert rule

Create an alert rule.

Create contact

Add a Contact to the Organization with the given internal `id`.

Create organization

Create a new Organization for the calling account.

Create tag

Create a new user-defined tag.

Cycle outlet power

Power-cycle a single outlet on a host device (PoE switch / PDU).

Delete alert rule

Delete an alert rule by ID.

Delete contact

Permanently delete a Contact from the Organization with the given internal `id`.

Delete device

PERMANENTLY delete one or more device records from a collector: the device and its history are removed entirely.

Delete driver

Permanently delete a driver from the account.

Delete organization

Permanently delete an Organization.

Delete tag

Delete a user-defined tag by ID.

Detach driver

Remove the binding between a driver and a device on the given collector.

Detach sensor

Detach a preconfigured (overlay) sensor from a device.

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.

Device performance

Fetch device performance metrics including round-trip delay, packet loss, uptime, SNMP sensor values, and disk usage over the last 7 days.

Execute driver

Run an action of a driver against a device.

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.

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 statuses currently present in the data.

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.

Get collector capabilities

Inspect what the customer's Collector can actually run.

Get collector credential coverage

Collector-wide credential audit.

Get config backup entry

Returns a single configuration backup snapshot's text for a device.

Get config backup status

Lists 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), status (ENABLED / DISABLED), failed-inspection count, and last inspection time.

Get create tag form

Shows an interactive form to create a new custom tag, with a name field and a color picker.

Get device alert rule bindings

List alert rules bound to a specific device, including device-level bindings and bindings to variables owned by that device.

Get device alerts

Retrieve alert and monitoring configuration status for a specific device.

Get device credentials

Per-device credential status drill-down.

Get device history

Returns the per-device History / Event Log for a single device: the chronological stream of events the device generated, most recent first.

Get device interfaces

Lists the SNMP-collected interfaces on a device.

Get device metrics

Fetch summarised time-series analytics for one or more named metrics on a device within a time range.

Get driver catalog

Lists the account-wide catalog of drivers available for attaching and executing on devices.

Get driver template

Fetch a single driver template, including its full JS code body and requirement metadata (`requirements.

Get interface traffic

Returns traffic counters for one or more device interfaces over a time range.

Get network configuration

Fetch what a collector actually scans, to answer 'why isn't this device discovered?

Get organization

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

Get snmp credentials form

Shows an interactive form to set or update SNMP credentials on a specific device.

Get uptime

Returns uptime stats for a collector or device over a time range: total uptime percentage, online_seconds, total_seconds, and the list of downtime intervals.

Inspect driver

Static analysis of a driver's JS against the Domotz sandbox.

List alert rules

Lists alert rule definitions in the account.

List collector metrics

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

List communication channels

List the user's notification channels (email, webhook, Slack, etc.

List config backup history

Lists configuration backup snapshots for a device on a collector, newest first.

List device drivers

Lists drivers currently attached to a device.

List device metrics

List everything monitorable on a device.

List device profiles

Lists device profiles in the account.

List device sensors

Lists the sensors currently attached to a device, merged across CUSTOM_OID, TCP, CUSTOM_DRIVER, and PRECONFIGURED kinds.

List device types

Returns the device-type catalog used to classify devices (router, switch, AP, server, etc.

List driver templates

List shared driver templates the account can start from.

List metric functions

List the evaluation functions (e.

List organizations

List the account's Organizations with their Contacts and bound Collector ids.

List preconfigured sensors

Returns the account-wide catalog of preconfigured sensors available to attach via `attach_sensor(sensor_spec={kind: 'overlay', overlay_id: .

List tags

Returns the account-wide catalog of user-defined tags applied to devices and collectors.

List variable alert rule candidates

List alert rules that could be bound to a specific device variable.

Manage external hosts

Add or remove an external host on a collector.

Manage ip scan policy

Manage the collector's forced IP scan policy: extra addresses the collector must probe on top of what it discovers by itself.

Manage routed networks

Add, update or remove a routed network on a collector.

Network topology

Returns the network topology discovered by a single collector: device-to-device links and per-outlet (port) details.

Resolve alert

Permanently resolve one or more alert incidents.

Save driver

Create or update a driver on the account.

Search alerts

Search alert history with filters.

Search audit logs

Search Domotz audit logs for the caller's organization.

Search collectors

Search and list Domotz collectors with filtering and pagination (zero-based: first page is page=0).

Search devices

Cross-account device search with filters and pagination (zero-based: first page is page=0).

Search organizations

List and filter the organizations visible to the calling user.

Set collector default snmp credentials

Set the collector's DEFAULT SNMP credentials — the ones used for devices that have no SNMP credentials of their own.

Set device credential

Set or overwrite a device credential.

Set device power

Change the power state of a device: turn it `on`, hold it `off`, `cycle` it, or issue a `software_reboot`.

Set interfaces policy

Set which of the collector's own network interfaces take part in discovery, by name.

Snooze collector alerts

Snooze (temporarily mute) all alerting for a collector for a maintenance window.

Submit feedback

Submit feedback about a gap in available MCP tools or data.

Unbind alert rule from collector

Unbind an alert rule from a collector.

Unbind alert rule from device

Unbind an alert rule from a device.

Unbind collector from organization

Unbind a Collector from an Organization (addressed by its internal `id`).

Unsnooze collector alerts

Resume alerting on a collector immediately, cancelling any active snooze/maintenance window set by `snooze_collector_alerts`.

Update alert rule

Update an existing alert rule in place, preserving its device/collector/variable bindings and alert history (unlike deleting and recreating).

Update collector metadata

Update editable metadata on a collector (the on-site monitoring agent).

Update collector monitoring settings

Update how the collector monitors, as opposed to what it monitors.

Update contact

Update a Contact on the Organization with the given internal `id`.

Update device metadata

Update editable metadata fields on a device: `name`, `importance` (important or not important), `zone`, `room`, `serial`, `notes` (max 256 chars).

Update device monitoring state

Manage or unmanage one or more devices by changing their monitoring state.

Update organization

Update an existing Organization by its internal `id`.

Update tag

Rename an existing user-defined tag, change its colour, or both.

SETUP GUIDE

Connect Domotz MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/openai @ai-sdk/mcp
Install the Composio SDK for Python or TypeScript
2

Initialize Client and Create Tool Router Session

typescript
import { Composio } from '@composio/core';

const composio = new Composio({ apiKey: 'your-api-key' });
const session = await composio.create('your-user-id');
console.log(`Tool Router session created: ${session.mcp.url}`);
Import and initialize the Composio client, then create a Tool Router session for Domotz MCP
3

Connect to AI Agent

typescript
import { openai } from '@ai-sdk/openai';
import { experimental_createMCPClient as createMCPClient } from '@ai-sdk/mcp';
import { generateText } from 'ai';

const client = await createMCPClient({
  transport: {
    type: 'http',
    url: session.mcp.url,
    headers: {
      'x-api-key': 'your-composio-api-key',
    },
  },
});

const tools = await client.tools();
const { text } = await generateText({
  model: openai('gpt-4o'),
  tools,
  messages: [{
    role: 'user',
    content: 'YOUR_SPECIFIC_PROMPT_HERE'
  }],
  maxSteps: 5,
});

console.log(`Agent: ${text}`);
Use the MCP server with your AI agent (Anthropic Claude or Mastra)
SETUP GUIDE

Connect Domotz MCP API Tool with your Agent

1

Install Composio

typescript
npm install @composio/openai
Install the Composio SDK
2

Initialize Composio and Create Tool Router Session

typescript
import OpenAI from 'openai';
import { Composio } from '@composio/core';
import { OpenAIResponsesProvider } from '@composio/openai';

const composio = new Composio({
  provider: new OpenAIResponsesProvider(),
});
const openai = new OpenAI({});
const session = await composio.create('your-user-id');
Import and initialize Composio client, then create a Tool Router session
3

Execute Domotz MCP Tools via Tool Router with Your Agent

typescript
const tools = session.tools;
const response = await openai.responses.create({
  model: 'gpt-4.1',
  tools: tools,
  input: [{
    role: 'user',
    content: 'YOUR_SPECIFIC_PROMPT_HERE'
  }],
});
const result = await composio.provider.handleToolCalls(
  'your-user-id',
  response.output
);
console.log(result);
Get tools from Tool Router session and execute Domotz MCP actions with your Agent

Why Use Composio?

AI Native Domotz MCP Integration

  • Supports both Domotz MCP and direct API based integrations
  • Structured, LLM-friendly schemas for reliable tool execution
  • Rich coverage for reading, writing, and querying your Domotz MCP data

Managed Auth

  • Built-in OAuth handling with automatic token refresh and rotation
  • Central place to manage, scope, and revoke Domotz MCP access
  • Per user and per environment credentials instead of hard-coded keys

Agent Optimized Design

  • Tools are tuned using real error and success rates to improve reliability over time
  • Comprehensive execution logs so you always know what ran, when, and on whose behalf

Enterprise Grade Security

  • Fine-grained RBAC so you control which agents and users can access Domotz MCP
  • Scoped, least privilege access to Domotz MCP resources
  • Full audit trail of agent actions to support review and compliance
FRAMEWORKS

Use Domotz MCP with any AI Agent Framework

Choose a Framework you want to connect Domotz MCP with

FAQ

Frequently asked questions

Yes, Domotz MCP requires you to configure your own API key credentials. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Composio is SOC 2 and ISO 27001 compliant with all data encrypted in transit and at rest. Learn more.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Start with Domotz MCP.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Domotz MCP tool your agent needs.Free to start.

Start building