This server connects AI assistants to Domotz for network monitoring and management, enabling actions across multiple domains via a navigation tool and status check.
Navigate domains: Use domotz_navigate to switch between agents, devices, metrics, network, alerts, and power domains.
Check connection status: Use domotz_status to verify the Domotz API connection and see available domains.
Manage agents: Work with Domotz monitoring agents (collectors/sites).
View/manage alerts: Monitor and handle network alerts and alert profiles.
Monitor devices: Discover devices and check their status.
Access metrics: Retrieve network performance metrics (SNMP/variables).
Inspect network: Review topology, interfaces, and configuration.
Manage power: Control PDUs and outlets for managed devices.
A Model Context Protocol (MCP) server for Domotz network monitoring and management. Enables AI assistants to monitor network devices, view alerts, check device status, and manage network infrastructure.
This is a Model Context Protocol (MCP) server that connects Claude (or any MCP-compatible AI) to your Domotz environment.
Part of the MSP Claude Plugins ecosystem — a growing suite of AI integrations for the MSP stack. Built by MSPs, for MSPs.
npm install @wyre-ai/domotz-mcpRelated MCP server: network-mcp-server
Set the following environment variables:
Variable | Required | Description |
| Yes | Your Domotz API key |
| No | API region: us or eu (default: us) |
| No | Transport mode: stdio (default) or http |
Add to your Claude Desktop claude_desktop_config.json:
{
"mcpServers": {
"domotz-mcp": {
"command": "npx",
"args": ["@wyre-ai/domotz-mcp"],
"env": {
"DOMOTZ_API_KEY": "your-domotz-api-key"
}
}
}
}claude mcp add domotz-mcp \
-e DOMOTZ_API_KEY=your-value \
-- npx -y @wyre-ai/domotz-mcpdocker build -t domotz-mcp .
docker run \
-e DOMOTZ_API_KEY=your-value \
-p 8080:8080 domotz-mcpManage Domotz monitoring agents
View and manage network alerts
Device discovery and status monitoring
Network performance metrics
Network topology and configuration
Power management for managed devices
# Clone the repository
git clone https://github.com/WYRE-AI/domotz-mcp.git
cd domotz-mcp
# Install dependencies
npm install
# Build
npm run build
# Run tests
npm testContributions are welcome! Please see CONTRIBUTING.md if present, or open an issue to discuss changes.
Licensed under the Apache License, Version 2.0. See LICENSE for details.
Check Domotz API connection status and available domains.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It indicates a read-only check operation, which is appropriate, but lacks details on backend calls, authentication, or performance implications.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no extraneous words. Perfectly concise for a simple tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless tool with no output schema, the description covers the essential purpose. However, it omits details about the response format or what 'available domains' means, which could be slightly improved.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are zero parameters, so the description adds no parameter meaning. Baseline is 4 because no parameter documentation is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Check') and clearly specifies the resource ('Domotz API connection status and available domains'). It distinguishes itself from the sibling 'domotz_navigate' tool by focusing on status rather than navigation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when needing to verify connectivity or list domains, but provides no explicit guidance on when to avoid this tool or compare with siblings like 'domotz_navigate'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.4domotz_navigatedomotz_statusScored across 2 tools
The two tools have completely distinct purposes: one navigates to various domains, the other checks API status. No overlap or ambiguity.
Both tools follow the same 'domotz_verb' pattern with simple, clear verbs: 'navigate' and 'status'. Consistent and predictable.
With only 2 tools covering a wide range of domains (agents, devices, metrics, network, alerts, power), the tool surface is too thin for the apparent scope. Likely requires heavy parameterization in a single tool.
The server only provides navigation to domains and status check, but no actual CRUD or action tools for those domains. This is severely incomplete for practical management tasks.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
