Skip to main content
Glama
Ringosystems

Homey-Wan-Kenobi-MCP

by Ringosystems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Homey-Wan-Kenobi-MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      2
      47
      38 PyPI
      MIT

    • 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.
      -

    • homekit-cli

      l3wi
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for inspecting and controlling Apple HomeKit accessories, scenes, automations, and more via the HomeClaw app, enabling natural language interaction with your smart home.
      9 npm
      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
      69 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

    A3.9/5.0

    Scored across 60 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose, with detailed descriptions that prevent ambiguity. For example, create_advanced_flow and create_flow target different flow types, while analyze_app_usage is advisory and separate from list_apps. No two tools overlap in function.

    Naming Consistency4/5

    Most tool names follow a verb_noun pattern (e.g., list_devices, create_backup, set_device_capability). A few outliers like 'analyze_app_usage' and 'homey_api_call' break the pattern but are still readable. Overall, the naming is mostly consistent and predictable.

    Tool Count2/5

    With 60 tools, the count is high and exceeds the 'too many' threshold from the calibration. While the domain is broad, the number may overwhelm agents and increase navigation difficulty. A more focused set could improve coherence.

    Completeness5/5

    The tool surface covers all major aspects of Homey management: flow CRUD, device control, energy monitoring, network diagnostics, system administration, and more. There are no obvious gaps; even advanced operations like Zigbee diagnosis and API escape hatches are included.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources