Skip to main content
Glama
decline27

Homey MCP Server

by decline27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Homey MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Server for Homey API

      NdyGen
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to interact with Homey home automation systems for managing flows, devices, and zones. Perfect for bulk automation tasks like batch renaming flows, organizing them into folders, and managing devices across zones through natural language.
      -

    • homey-mcp

      tim661811
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to control a Homey Pro smart home hub, create automation flows from natural language, and query device and energy history.
      36
      8 npm
      MIT

    • Homey MCP Server

      homey-mcp
      A
      license
      A
      quality
      D
      maintenance
      Enables natural language control of Homey Pro smart home systems, including devices, flows, zones, energy monitoring, weather, alarms, and system management, with 43 tools and troubleshooting prompts.
      43
      8 npm
      MIT

    • home-assistant-mcp

      mattmaas
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read Home Assistant entity states, call any service, and optionally apply named scene presets from a catalog using plain-English descriptions.
      46 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.6/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action (devices, sensors, zones, flows, energy, insights). Even similar tools like list_flows vs list_advanced_flows are clearly differentiated by type. No overlapping purposes that would cause misselection.

    Naming Consistency5/5

    All tools follow the consistent 'homey_verb_noun' pattern with snake_case. Verbs like list, get, find, control, set, run are used predictably. The naming convention is uniform and easy to infer.

    Tool Count4/5

    19 tools is slightly above the typical well-scoped range, but the broad scope of a smart home hub (devices, zones, flows, energy, insights) justifies the count. Each tool serves a distinct purpose, so it doesn't feel excessive.

    Completeness4/5

    The tool surface covers core home automation workflows: reading device/sensor state, controlling devices, managing/running flows, and accessing energy/insight data. Minor gaps exist (e.g., no create/update/delete for flows or zones, no bulk zone control beyond lights), but these are workable and typical for a control-oriented server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources