Skip to main content
Glama
cacack

mcp-server-zwave-js-ui

by cacack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-server-zwave-js-ui

No user-submitted related servers found.

    Related Servers

    • Home Assistant MCP Server by homeassistant-ai

      Home Assistant MCP Serverofficial

      homeassistant-ai
      A
      license
      A
      quality
      A
      maintenance
      A comprehensive MCP server that enables AI assistants to interact with Home Assistant, control smart home devices, query states, execute services, and manage automations via natural language.
      77
      31,054 PyPI
      4,867
      MIT

    • 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
      113 npm
      MIT

    • mcps

      klausmark
      A
      license
      Not graded
      quality
      B
      maintenance
      A thin MCP server that securely enables AI agents to interact with Home Assistant, Mealie, and Nirvana via tools for automation, recipe management, and task tracking, while keeping credentials hidden.
      MIT

    • openhab

      deswong
      A
      license
      C
      quality
      C
      maintenance
      MCP server for OpenHAB v5+ that exposes the entire REST API as tools for AI models, enabling complete control over items, things, rules, persistence, and semantic model.
      25
      7
      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

    A3.9/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct Z-Wave operation (e.g., add association vs remove association, begin inclusion vs stop inclusion, node info vs node config vs node values). There is no functional overlap between tools, and descriptions clearly differentiate their purposes.

    Naming Consistency5/5

    All tool names follow a consistent 'zwave_verb_noun' pattern in snake_case (e.g., zwave_add_association, zwave_list_nodes, zwave_set_value). Verbs are action-oriented and nouns clearly indicate the resource, making the convention predictable across all 24 tools.

    Tool Count4/5

    24 tools is on the higher side of typical, but the Z-Wave domain requires many distinct operations (network management, node configuration, value control, associations). Each tool serves a well-defined purpose without redundancy, so the count is justified and not excessive.

    Completeness4/5

    The tool surface covers core Z-Wave workflows: node discovery, configuration, value setting, associations, inclusion/exclusion, route rebuilding, and firmware status. Minor gaps exist (e.g., no firmware update trigger, incomplete S2 secure inclusion), but these are explicitly noted and do not significantly impair common tasks.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources