Skip to main content
Glama
dmanfx

mcp-hs4

by dmanfx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to mcp-hs4

No user-submitted related servers found.

    Related Servers

    • Home Assistant Admin MCP

      lemanjo
      A
      license
      Not graded
      quality
      A
      maintenance
      A safety-oriented Model Context Protocol (MCP) server for inspecting, controlling, diagnosing, and selectively administering a Home Assistant instance.
      MIT

    • Hubitat MCP Server

      solaegis
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Hubitat Elevation hubs that controls devices via the Maker API, with optional gated access to undocumented admin routes, supporting device listing, command sending, virtual device and hub variable automation for Rule Machine, and hub management features.
      8
      MIT

    • mcp-ha

      Devitek
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Home Assistant that lets you control and query your smart home through natural language via MCP clients. Provides tools for entities, devices, services, automations, scripts, history, add-ons, and system info, with read-only access by default and optional configurable write support.
      1
      MIT

    • AutoFlow Gateway

      lidicn
      A
      license
      Not graded
      quality
      B
      maintenance
      Central MCP gateway for smart home automation, enabling agents to safely control Home Assistant and Node-RED with identity-based access, human confirmation for writes, and a WebUI for governance.
      1
      MIT

    • hass-mcp

      TheWhykiki
      A
      license
      A
      quality
      D
      maintenance
      MCP server for controlling and querying Home Assistant via its REST API, exposing tools to get entity states, list all states, and call services.
      16
      111 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

    B3.2/5.0

    Scored across 63 tools

    Disambiguation5/5

    All tools are distinctly scoped within hierarchical namespaces (health, resolve, devices, events, cameras, admin, etc.), with clear and non-overlapping responsibilities. Even seemingly similar tools like 'hs4.intent.device_set_by_name' and 'hs4.devices.set' have different use cases (natural language resolution vs direct control).

    Naming Consistency5/5

    The naming follows a uniform 'hs4.<domain>.<subdomain>.<action>' pattern with snake_case throughout. Each tool's name precisely reflects its function and place in the hierarchy, making navigation predictable.

    Tool Count3/5

    At 63 tools, the count is high but arguably justified given the breadth of HomeSeer HS4 (devices, events, cameras, plugins, interfaces, users, system admin). However, it borders on overwhelming and could be trimmed by merging some specialized admin tools.

    Completeness5/5

    The tool set provides full CRUD and lifecycle management for all major entities (users, plugins, interfaces, cameras, events, devices) plus system operations, health checks, natural language resolution, and audit logging. No obvious gaps for the stated purpose of managing an HS4 server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources