Skip to main content
Glama
jacedomotz

Domotz MCP Server

by jacedomotz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Domotz MCP Server

No user-submitted related servers found.

    Related Servers

    • datto-rmm-mcp

      wylienorthwind
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to interact with Datto RMM accounts for device, alert, site, and quick job management through natural language.
      Apache 2.0

    • IT Glue MCP Server

      nessit-gness
      A
      license
      A
      quality
      C
      maintenance
      Provides Claude with access to IT Glue documentation and asset management, enabling search, retrieval, and creation of organizations, configurations, locations, passwords, documents, attachments, flexible assets, and user activity metrics through the IT Glue API.
      28
      Apache 2.0

    • firewalla-mcp

      djuntgen
      A
      license
      B
      quality
      A
      maintenance
      Exposes the Firewalla MSP API as tools for Claude Code and other MCP clients, enabling natural-language management of Firewalla boxes, alarms, rules, devices, flows, target lists, and trends with full read/write capabilities.
      19
      MIT

    • mcp-it-ops

      bastiaan365
      F
      license
      A
      quality
      C
      maintenance
      Exposes homelab and IT-ops tools to Claude, including system health monitoring, Grafana alert states, Docker container status, Loki logs, SMART disk health, and more.
      8
      1
      -

    • unifi-mcp

      JohnGilligan2
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only querying of a UniFi fleet via the Site Manager API and per-console connector proxy, allowing users to list hosts, sites, devices, ISP metrics, and live network clients through Claude.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a clearly distinct domain (agents, devices, monitoring, alerts, network, configuration, power, drivers, inventory, account, plus three composite helpers). There is no overlap in purpose; an agent can easily distinguish which tool to use based on the operation needed.

    Naming Consistency4/5

    All tools use the 'domotz_' prefix with a descriptive noun or verb phrase. Most are nouns (e.g., domotz_agents, domotz_devices) but three composite tools use verbs (get_device_full_status, get_agent_overview, search_devices), introducing a minor inconsistency. Overall pattern is clear and predictable.

    Tool Count5/5

    The tool count of 13 is well-scoped for a comprehensive network monitoring platform. Each tool covers a distinct area, and the set is neither too lean nor overwhelming. The three composite tools provide efficiency without bloating the surface.

    Completeness5/5

    The tool surface is remarkably complete, covering agent and device management, sensor configuration and monitoring, alerts, network policies, configuration backups, power management, custom drivers, inventory, and account info. Composite and search tools address common multi-step queries, leaving no obvious dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources