iaqualink-mcp
Related Servers
Alternatives to iaqualink-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to monitor and control Jandy iAqualink pool and spa equipment, including device status, power toggling, temperature settings, and lighting effects.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible assistants to retrieve live data from an iopool pool account, including water temperature, pH, ORP, running mode, and filtration recommendations, and to list the account's pools. Access is authenticated with the user's own iopool API key, via OAuth or a direct bearer header.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.MIT
- AlicenseNot gradedqualityDmaintenanceAccess Home Assistant data and control devices (lights, switches, thermostats, etc).6 npm574Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables 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.58 PyPI2MIT
- AlicenseAqualityCmaintenanceEnables an assistant to locally discover and control supported Sleepme bed devices, check water status, adjust temperatures, retrieve Sleep Tracker reports, and manage saved routines.15MIT
TDQS
Scored across 19 tools
Most tools target a distinct resource+action (systems, status, schedules, OneTouch, pump speeds), and descriptions explicitly scope iAqua vs eXO behavior. Two real overlap points remain: iaqualink_set_equipment covers eXO 'production'/'boost' chlorine control while iaqualink_set_chlorinator sets output percentage, and iaqualink_set_aux turns light circuits on/off while iaqualink_set_light sets brightness/color. iaqualink_check_panel vs iaqualink_healthcheck is also a fine distinction an agent must reason about.
All names share the iaqualink_ prefix and snake_case verb_noun structure (list_systems, get_status, set_equipment, add/edit/delete_schedule). The only deviation is iaqualink_healthcheck, which omits a verb, and the schedule tools split awkwardly across set_schedule (eXO) versus add/edit/delete_schedule (iAqua) for what is nominally one concept.
Nineteen tools is on the heavy side, but the server genuinely spans two hardware families plus schedules, OneTouch scenes, VSP speeds, and diagnostics, so most tools earn their place. A few could be collapsed — set_chlorinator largely duplicates the eXO branch of set_equipment, and check_panel/healthcheck are adjacent diagnostics.
Coverage is strong for a control server: discovery, status, equipment/aux/light/temperature writes, full schedule CRUD for iAqua panels, OneTouch and pump-speed management, plus healthcheck and panel diagnostics. Gaps exist on the eXO side, which has list+set schedule but no add or true delete (only a disable-to-00:00), and there is no history/energy/log surface.