Skip to main content
Glama
eliseorobles

OpenEcoBee MCP

by eliseorobles
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to OpenEcoBee MCP

No user-submitted related servers found.

    Related Servers

    • ecobee-mcp

      BrianVia
      A
      license
      Not graded
      quality
      C
      maintenance
      Reads thermostat status and controls HVAC modes, holds, schedules, comfort sensors, settings, vacations, fan runtime, and on-screen messages for a single thermostat account, hosted remotely on Cloudflare Workers with bearer-protected, stateless access.
      96 npm
      MIT

    • myUplink MCP Server

      Alastair-Pandelus
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects MCP clients such as Claude to a NIBE myUplink heat-pump account, letting users list systems and devices, read sensor values and common parameters, check alarms, view smart-home zones, and write settings where scopes allow. Handles the OAuth2 authorization-code and client-credentials flows, refreshing tokens automatically while keeping credentials in a local .env file.
      MIT

    • Sonoff MCP Server

      mrkutin
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to control Sonoff smart-home devices through the eWelink Cloud API, with tools for device listing, switching, thermostat control, and sensor data retrieval.
      -

    • Plugwise MCP Server

      Tommertom
      A
      license
      A
      quality
      D
      maintenance
      Enables control and monitoring of Plugwise smart home devices including thermostats, switches, and energy meters with automatic network discovery. Supports temperature control, energy monitoring, and multi-hub management through natural language commands.
      16
      18 npm
      2
      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 5 tools

    Disambiguation4/5

    list_thermostats and get_thermostat_status both read thermostat state and their boundaries blur, since list_thermostats already returns temperatures and setpoints. However, the plural listing vs. single-thermostat detail distinction and the write actions (set_temperature, set_hvac_mode, resume_schedule) are otherwise clearly separable.

    Naming Consistency5/5

    All tools follow a clean snake_case verb_noun pattern: list_thermostats, get_thermostat_status, set_temperature, set_hvac_mode, resume_schedule. Verbs are consistently action-oriented and nouns are clear.

    Tool Count5/5

    Five tools is well-scoped for a thermostat controller: discovery, status read, temperature hold, mode change, and schedule resume. Each tool earns its place with no filler.

    Completeness4/5

    The surface covers the core read/set/resume lifecycle of thermostat control, but lacks operations like viewing the programmed schedule, setting fan/humidity modes, or canceling a hold explicitly. Minor gaps an agent can mostly work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources