Domotz MCP server

What the model can do

Domotz network monitoring: collectors (sites) with status, team and organization, the devices each one sees with status, importance, type, vendor, model, zone and tags, one device's detail and inventory fields, alerts by severity and status in a period, a device's up and down history, organizations, tags and shared alert profiles. Never returns IP or MAC addresses, ports or credentials. When asked, can resolve an alert, rename or annotate a device and set its importance or inventory fields, tag it, exclude it from monitoring, set it managed or unmanaged, back up its configuration, apply or remove an alert profile, turn a device or power outlet on, off or cycle it, delete a device, create a tag and add an organization contact.

Reads

• domotz_list_collectorsDomotz collectors (one per monitored site or network): id, name, status, team, organization, licence and version.
• domotz_list_devicesDevices one Domotz collector sees: id, name, status (ONLINE, OFFLINE, DOWN), importance, type, vendor, model, OS, zone, room…
• domotz_get_deviceOne Domotz device in detail: status, importance, type, vendor, model, OS, serial, firmware, zone, room, notes, tags, and its inventory fields.
• domotz_list_alertsAlerts raised by Domotz alert rules in a period (default the last 7 days, newest first): severity (Critical, High, Warning, Info), Open or Resolved…
• domotz_device_historyA Domotz device's state changes in a period (default the last week): when it went UP or DOWN, was first seen, or changed address…
• domotz_list_organizationsOrganizations (customers or sites groups, for MSPs) in Domotz: id, name, external reference and the collectors in each.
• domotz_list_tagsDomotz tags: id, name, colour and how many devices and collectors carry each.
• domotz_list_alert_profilesShared alert profiles set up in the Domotz Portal: id, name, whether enabled, and the events each one sends to its email…

Acts, when you ask

These change something in Domotz. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• domotz_resolve_alertMarks an open Domotz alert resolved, recording the API key's user as the resolver; Domotz may send a resolved notice to the profile's channels.
• domotz_update_deviceChanges one property of a Domotz device: its name, type, vendor or model as the team sees them, its importance (VITAL or FLOATING…
• domotz_set_inventory_fieldSets an inventory field on a Domotz device (asset tag, owner, purchase date or whatever the account's inventory defines).
• domotz_tag_devicePuts an existing Domotz tag on a device.
• domotz_untag_deviceTakes a Domotz tag off a device.
• domotz_create_tagCreates a Domotz tag with a name and colour, for the whole account.
• domotz_add_organization_contactAdds a contact (name and email, optional phones) to a Domotz organization.
• domotz_set_monitoring_stateSets a Domotz device MANAGED (monitored; uses one per-device licence, which may cost money) or UNMANAGED (frees it).
• domotz_backup_device_configTells the collector to back up a device's configuration now (switches, routers and firewalls with configuration management).
• domotz_exclude_deviceExcludes a device from Domotz monitoring, so the collector ignores it: no status, no alerts.
• domotz_apply_alert_profileApplies a shared alert profile to a Domotz device, so its events go to that profile's email, webhook, Slack or ticketing channels from now on.
• domotz_remove_alert_profileRemoves a shared alert profile from a Domotz device, so its events stop reaching that profile's channels.
• domotz_device_powerSends a power command to a Domotz device: on, off, cycle (off then on) or software-reboot.
• domotz_outlet_powerSwitches one outlet of a managed PDU or smart power strip on, off, or cycles it, cutting power to whatever is plugged in.
• domotz_delete_devicePermanently deletes a device from a Domotz collector, with its history, tags and inventory.

Connect it

First connect Domotz on Dashboard → Connections, then add Memtro to your client once. The Domotz tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Domotz connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which devices at the HQ site are down?
• › What critical alerts are still open this week?
• › How often did the core switch go down in the last week?
• › Which vital devices are tagged printer?
• › Power-cycle outlet 4 on the comms room PDU.

Questions

Is this an official Domotz MCP server?

No. It is Memtro's MCP server with Memtro's Domotz connector behind it: the connector reads Domotz through its API with the credentials you connect on Dashboard → Connections, and Domotz publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Domotz?

Only when you ask, and only what it has been granted: resolve an open alert; rename a device or set its importance, type, vendor, model, zone, room, serial or notes; set a device inventory field; tag a device; remove a tag from a device; create a tag; add a contact to an organization; set a device managed or unmanaged (per-device licensing); back up a device's configuration; exclude a device from monitoring; apply a shared alert profile to a device; remove an alert profile from a device; turn a device on or off, power-cycle or reboot it; turn a power outlet on or off, or cycle it; delete a device. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server