Skip to main content
Glama
solaegis

Hubitat MCP Server

by solaegis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Hubitat MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-hs4

      dmanfx
      A
      license
      B
      quality
      C
      maintenance
      MCP server for controlling HomeSeer HS4 with safe, auditable, and guarded write operations.
      63
      1
      MIT

    • Hubitat MCP Server

      jgitta
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to list, search, query, and control Hubitat home automation devices from MCP-compatible AI assistants like Claude Desktop.
      MIT

    • shelly-mcp

      Buggy1111
      A
      license
      A
      quality
      B
      maintenance
      MCP server for the entire Shelly smart-home ecosystem, enabling local-first control, automation, and energy monitoring of Shelly devices with cloud fallback.
      47
      MIT

    • mobilerun-mcp

      droidrun
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the Mobilerun platform, exposing tools for device control, workflow automation, task management, and platform operations via a stateless HTTP or stdio interface with bearer-token authentication and policy-based access control.
      Apache 2.0

    • mcp-tahoma

      pierresouchay
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for controlling Somfy TaHoma devices locally via the box's API, without cloud dependency.
      -

    • hass-mcp-server

      jarahkon
      A
      license
      B
      quality
      C
      maintenance
      MCP server for full Home Assistant control, enabling AI agents to manage dashboards, automations, files, apps, entities, and more via REST API, WebSocket, and SSH.
      66
      90 npm
      MIT
    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 8 tools

    Disambiguation5/5

    Every tool targets a distinct resource (hub variable vs device) and action (list/get/send/set), and the descriptions explicitly provide 'Do NOT use when' guidance to steer agents away from wrong choices. The get vs list vs send tools are clearly separated by their 'Use when'/'Do NOT use when' annotations, leaving no realistic ambiguity.

    Naming Consistency4/5

    The naming follows a consistent hubitat_verb_noun pattern (hubitat_list_devices, hubitat_get_device, hubitat_send_command). Minor deviations: 'hubitat_list_virtual_devices' reads more as an adjective-modifier than a pure noun, and set_color/send_command/hub_variable all mix nouns, but the pattern is mostly uniform with one verb-noun structure throughout.

    Tool Count5/5

    8 tools is a well-scoped count for a home-automation hub server. Each pair (list/get, get/send, get_device_commands/send_command, list/get hub_variable) earns its place, and the set covers discovery, control, color, and rule-machine levers without bloat.

    Completeness4/5

    The surface covers device discovery, state querying, command listing, generic command sending, and color setting, plus virtual-switch and hub-variable rule triggers. Minor gaps: there's no tool for device detail beyond get_device or updating device config, but the core workflows (discover, query, control, trigger) are all covered with no dead-end operations.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources