Skip to main content
Glama
caseman72

Wyzer MCP Server

by caseman72
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to Wyzer MCP Server

No user-submitted related servers found.

    Related Servers

    • io.github.Evin009/smartrent

      Evin009
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables Claude to control SmartRent smart home devices such as locks, thermostats, light switches, and sensors through natural conversation.
      5
      MIT

    • hass-mcp

      HiTechLabTN
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server for Home Assistant integration with Claude and other LLMs, enabling querying and controlling Home Assistant entities, automations, and dashboards.
      29
      MIT

    • meticulous-mcp

      NatiCha
      A
      license
      A
      quality
      D
      maintenance
      MCP server for controlling Meticulous espresso machines via Claude and other AI clients.
      22
      109 npm
      MIT

    • Hass-MCP

      voska
      A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to interact directly with Home Assistant, allowing them to query device states, control smart home entities, and perform automation tasks.
      16
      340
      MIT

    • elgato-keylight

      butterflyskies
      A
      license
      A
      quality
      C
      maintenance
      MCP server for controlling Elgato Key Lights. Enables turning lights on/off, adjusting brightness and color temperature, applying presets, and triggering effects via Claude.
      13
      Apache 2.0
    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.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools are clearly distinct per device type (purifier, plug, switch, thermostat), and control_* vs get_device_status vs list_devices are well-separated. Minor potential confusion between control_plug and control_switch, and the special combined thermostat+plug behavior in control_thermostat could be overlooked, but descriptions mitigate this.

    Naming Consistency4/5

    The control_* verb-noun pattern is used consistently for four device actions, and list_devices/get_device_status/get_api_status follow a verb_noun get_/list_ pattern. Minor deviation: control_thermostat spans two devices, and the get_/list_ mix is slight, but overall the schema is predictable and readable.

    Tool Count5/5

    Seven tools is an appropriate, well-scoped surface for a home IoT control server covering discovery, per-device control, status retrieval, and API health—all within the ideal 3-15 tool range with no redundancy.

    Completeness4/5

    The surface covers discovery, status, and control for four device types, plus API health—a solid set. Minor gaps include no bulk control, no scheduling, and no device registration/removal, but core lifecycle (list, get status, control) is fully covered and agents won't dead-end.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources