Domotz MCP
Domotz MCP lets agents inspect and manage authorized network-monitoring data, devices, alerts, sites, and IT operations through Domotz.
Verdict
Common use cases
- Check which devices went offline overnight
- Pull uptime reports for client networks
- Troubleshoot connectivity issues during incidents
- Review alert history before standup
- Monitor bandwidth usage across sites
Integration
- Vendor
- Domotz MCP
- Category
- other
- Auth
- API_KEY
- Composio slug
domotz_mcp
Tools
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Domotz MCP in the list and click Connect. 3. Log into your Domotz account in a separate tab and go to Settings > API to generate a new API key. 4. Copy the key and paste it into the Switchy connection dialog, then click Authorize. 5. Switchy will verify the key has access to your monitored devices. 6. Once connected, open any Project and type '@Domotz' followed by a request like 'show me all offline devices' to test the connection. 7. If the MCP responds with device data, the integration is working. 8. If you see an authentication error, double-check the API key hasn't expired and has the correct read permissions in Domotz.
What teammates see: by default, memories from Domotz MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Offline Device Report
@Domotz show me all devices that are currently offline, grouped by network, with the last seen timestamp for each.
Weekly Uptime Summary
@Domotz give me uptime percentages for all critical devices over the last 7 days, sorted by lowest uptime first.
Recent Alert History
@Domotz list all alerts from the past 24 hours, including device name, alert type, and timestamp.
Bandwidth Usage Check
@Domotz show me current bandwidth usage for each monitored network, highlighting any that exceed 80% capacity.
Device Status by Location
@Domotz break down device status by location, showing online count, offline count, and any devices with warnings.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Domotz show me all devices on the main office network that are currently offline or have connectivity issues
Based on the main office network monitoring data, 3 devices are currently offline: HP LaserJet printer (192.168.1.45, last seen 2 hours ago), Conference Room TV (192.168.1.78, last seen 35 minutes ago), and Storage NAS (192.168.1.120, last seen 15 minutes ago). Additionally, the WiFi access point in the break room shows intermittent connectivity with 23% packet loss over the past hour. All other 47 monitored devices report normal status.
This example shows network device monitoring and status reporting. Requires API key with read access to your Domotz account. The actual device list and network topology depend on what you've configured in Domotz — this illustrative output assumes a typical small office setup.
@Domotz create an alert rule to notify me when any device on the warehouse network goes offline for more than 10 minutes
Alert rule created successfully for warehouse network. Configuration: trigger when any device status changes to offline for 10+ consecutive minutes. Notifications will be sent via the channels configured in your Domotz account (email and webhook). The rule is now active and monitoring 18 devices on the warehouse network segment. You can modify notification channels or adjust the timeout threshold in your Domotz dashboard.
Demonstrates alert configuration capabilities. This action modifies your Domotz monitoring setup — the alert will fire for real network events going forward. Requires API key with write permissions. Notification delivery depends on your Domotz account's integration settings (Slack, email, etc.).
@Domotz analyze the uptime patterns for all critical infrastructure devices over the past 30 days and identify which ones need attention
Analyzing 30-day uptime data for 12 devices tagged as critical infrastructure: The warehouse router shows 97.2% uptime with 4 outage incidents (longest: 3.5 hours on Jan 15). The main office switch has 99.8% uptime — excellent. However, the backup internet gateway dropped to 89.1% uptime with frequent brief disconnections, suggesting ISP instability or hardware degradation. Recommendation: prioritize investigating the backup gateway and consider redundancy for the warehouse router given its business-critical role and recent extended outage.
Shows how the AI can synthesize historical monitoring data into actionable insights. The analysis quality depends on how you've tagged devices in Domotz and the completeness of your monitoring history. Rate limits may apply for large historical data queries — expect slower responses when analyzing months of data across many devices.
Use-case deep-dives
When Domotz MCP fits managed service provider workflows
A 6-person MSP team monitors 40 client networks and needs to surface device alerts in Slack without switching tabs. Domotz MCP is the right call if your team already uses Domotz for network monitoring and wants to query device status, uptime, or alert history from Switchy. The API_KEY auth means each team member can authenticate once and share queries in a channel. The trade-off: if you're not already a Domotz customer, the platform's pricing starts at enterprise tiers, so this MCP only makes sense when Domotz is your existing monitoring stack. If your team runs fewer than 20 client sites, a simpler ping monitor with webhook integrations may be cheaper. Use this MCP when Domotz is already your source of truth and you want to centralize network queries alongside support tickets.
Domotz MCP for internal IT teams managing office hardware
A 3-person IT team at a 200-employee company tracks printers, switches, and access points across four offices. Domotz MCP works here if the team needs to answer "which devices are offline?" or "what's the firmware version on the lobby switch?" without opening the Domotz dashboard. The MCP lets you pull device lists, check connectivity, and log historical data from Switchy's shared workspace. The boundary: if your inventory changes weekly (new hires, office moves), you'll spend more time updating Domotz than querying it. This MCP shines when your device topology is stable and the team's main job is reactive troubleshooting. If you're still choosing a monitoring platform, evaluate whether Domotz's feature set justifies the cost before committing to the MCP integration.
When Domotz MCP supports distributed operations teams
A retail chain's 4-person ops team monitors point-of-sale systems and Wi-Fi at 30 store locations. Domotz MCP is the right fit if the team already uses Domotz agents at each site and wants to run health checks from Switchy during morning standups. The MCP can surface which stores have connectivity issues, check device uptime, and pull alert logs without context-switching. The catch: if your stores have inconsistent internet or the Domotz agent goes offline, the MCP can't query that site's devices. This integration works best when network reliability is high and the team's workflow is "check status, escalate issues" rather than hands-on config changes. Use Domotz MCP when your monitoring is already centralized and you need faster access to device data across locations.
Frequently asked
What does the Domotz MCP do in Switchy?
The Domotz MCP connects your network monitoring infrastructure to Switchy's AI workspace. Your team can query device status, network topology, and alert history through natural language instead of logging into the Domotz dashboard. Useful for IT teams who want AI agents to pull diagnostics or check uptime without switching contexts.
Do I need admin access to generate the API key?
Yes. You'll need owner or admin permissions in your Domotz account to create an API key with sufficient scope. Standard user accounts can't generate keys that access network-wide device data. If you're not an admin, ask whoever manages your Domotz instance to provision the key and share it securely with your Switchy workspace owner.
Can it trigger actions like rebooting devices or changing configurations?
That depends on what Domotz exposes via its API and which tools this MCP implements. Most network monitoring platforms limit API write operations to avoid accidental outages. If you need to reboot devices or push config changes, check whether Domotz's API supports those actions — the MCP can only surface what the underlying platform allows.
Why use this instead of just checking the Domotz dashboard?
The MCP lets you ask questions like 'which devices went offline this week' or 'show me bandwidth spikes on the office router' without leaving Switchy. Your AI agent pulls the data, formats it, and answers in seconds. Faster than navigating tabs, filtering logs, or exporting CSVs. Best for teams who already live in Switchy and want monitoring insights inline.
Who on the team should connect this integration?
Whoever owns your Domotz account and understands which networks or device groups the team needs visibility into. That's usually your IT lead or network admin. Once connected, any Switchy user in the workspace can query the data through AI agents, but only the connector can rotate or revoke the API key.