OpenEcoBee MCP
Related Servers
Alternatives to OpenEcoBee MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI clients to read and control local ecobee thermostats over HomeKit, listing thermostats, getting status, setting or adjusting temperatures, changing HVAC modes, and holding or resuming comfort settings per thermostat or house-wide. Changes are constrained by guardrails such as setpoint limits, an optional read-only mode, and a per-thermostat hourly change cap, with every attempt logged.7344 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceEnables ChatGPT to connect to and interact with Strava via a stateless relay with browser-guided OAuth sign-in.MIT
- AlicenseNot gradedqualityCmaintenanceReads 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.109 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnects 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
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- AlicenseAqualityDmaintenanceEnables 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.1611 npm2MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.