Skip to main content
Glama
martellj

thermoslop

by martellj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to thermoslop

No user-submitted related servers found.

    Related Servers

    • Larnitech MCP

      mpopovych-thinkhome
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to connect to smart-home controllers to read device snapshots, watch live state changes, look up type-specific documentation and known vendor quirks, save and compare data snapshots, and perform guarded two-phase writes for lights, climate, blinds, sensors and meters. Writes stay disabled until explicitly enabled, are previewed and token-confirmed before execution, and report what actually landed on the device.
      39 PyPI
      1
      MIT

    • OpenEcoBee MCP

      eliseorobles
      A
      license
      A
      quality
      B
      maintenance
      Enables controlling ecobee thermostats from ChatGPT by connecting a user's ecobee account through normal browser sign-in, without an ecobee developer API key. Supports listing thermostats, reading status, setting temperature or HVAC mode, and resuming schedules.
      5
      MIT

    • 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.
      395 npm
      MIT

    • OmniButler

      Tiybai
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover, read and control smart-home devices from multiple vendors through a unified capability model, and to author and trigger YAML scenes that a local deterministic engine executes without the AI in the control loop. High-risk actions such as door locks and garage doors are held in a confirmation queue for a human, and every call is written to a local audit log.
      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.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool maps to a distinct action: listing devices, reading status, absolute setpoint, relative adjustment, mode, comfort preset, and clearing holds. set_temperature vs adjust_temperature overlap conceptually but the descriptions make the absolute-vs-delta distinction explicit, and get_status's no-argument mode slightly overlaps list_thermostats but reports different data.

    Naming Consistency5/5

    All seven tools follow a consistent snake_case verb_noun or verb_target pattern (list_thermostats, get_status, set_temperature, adjust_temperature, set_mode, set_comfort, resume_schedule). The set_/adjust_/resume_ verb families are used meaningfully and predictably.

    Tool Count5/5

    Seven tools is well-scoped for a thermostat control server, with each tool earning its place. There is no redundancy and no obvious filler.

    Completeness4/5

    Core lifecycle is covered: discovery, status, absolute and relative setpoint control, mode changes, comfort presets, and schedule resumption. Minor gaps exist (no fan control, no unpair/remove thermostat, no sensor-specific operations), but agents can accomplish the primary workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources