domotz-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOMOTZ_REGION | No | API region: us or eu | us |
| MCP_TRANSPORT | No | Transport mode: stdio or http | stdio |
| DOMOTZ_API_KEY | Yes | Your Domotz API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| domotz_navigateA | Navigate to a domain to access Domotz tools. Domains: agents (collectors/sites), devices (network devices), metrics (SNMP/variables), network (topology/interfaces), alerts (alert profiles), power (PDU/outlets). |
| domotz_statusA | Check Domotz API connection status and available domains. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored 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.