domotz

This MCP server provides Claude with access to Domotz through 10 category tools that cover 133 API actions. It translates natural language requests into Domotz API calls, enabling tasks such as listing collectors and devices, checking uptime histories, monitoring SNMP and TCP sensors, and retrieving configuration details or IP conflict information. You can ask Claude to summarize network inventories, fetch status histories, or perform operational actions like powering devices or backing up configurations depending on the available actions in each tool.

To use it, install and run the MCP server, configure Claude Desktop to point at the server (providing the full path to index.js and your API key), restart Claude Desktop, and then query Claude with natural language requests like, “Show me all offline devices,” or “List all collectors and their statuses.” Claude will route your query to the appropriate Domotz tool (e.g., domotz_devices, domotz_agents, domotz_monitoring) and present the results in a readable format. Each tool maps to a set of actions (for example domotz_agents supports actions such as list, uptime_history, and ip_conflicts) to perform specific operations against your Domotz account.

Prerequisites:

• A Domotz account with API access enabled
• Claude Desktop installed
• Node.js 18+ installed on the machine running the MCP server
• Your Domotz API Key

Step-by-step:

1. Clone the MCP server repository and install dependencies:

   • git clone https://github.com/jacedomotz/domotz-mcp-server.git
   • cd domotz-mcp-server
   • npm install

2. Prepare the MCP server configuration for Claude Desktop:

   • Copy claude_desktop_config.example.json to your Claude Desktop config location or edit your existing claude_desktop_config.json
   • In the mcpServers.domotz section, set:
     • command: "node"
     • args: ["/path/to/domotz-mcp-server/index.js"]
     • env.DOMOTZ_API_KEY: your Domotz API key
     • env.DOMOTZ_API_BASE_URL: the region URL (US or Europe) as appropriate

3. Start the MCP server (if not started by Claude Desktop):

   • Ensure Node.js is installed and accessible in your PATH
   • Run: node /path/to/domotz-mcp-server/index.js

4. Restart Claude Desktop to load the new MCP server configuration and verify:

   • In Claude, ask for a simple query like, "List my Domotz collectors" to confirm the integration works.

Tips and notes:

• Keep your Domotz API key secure; do not share your claude_desktop_config.json publicly.
• If you switch regions (US vs Europe), update DOMOTZ_API_BASE_URL accordingly.
• Use full-path index.js in the Claude config to avoid runtime path issues.
• If API calls fail, verify the API key and permissions, and ensure the server has network access to the Domotz API endpoint.
• The server exposes 10 category tools (domotz_agents, domotz_devices, domotz_monitoring, domotz_alerts, domotz_network, domotz_configuration, domotz_power, domotz_drivers, domotz_inventory, domotz_account). Each tool should be invoked via Claude through natural language prompts that map to specific actions within these tools.