hive-mcp
Related Servers
Alternatives to hive-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceUnofficial MCP server for Octopus Energy customers in the UK. Lets Claude and other AI assistants read your smart meter usage, costs, tariffs and bills, find the cheapest Agile half-hours and, if you allow it, manage Intelligent Octopus EV charging and join Saving Sessions. Read-only by default, with an optional audit log. Runs in Docker or as a one-click Claude Desktop bundle.201MIT
- AlicenseAqualityDmaintenanceAn unofficial MCP (Model Context Protocol) server that exposes a Vaillant heat pump's data to AI assistants like Claude. Query outdoor and room temperatures, hot water status, energy consumption, COP estimates, schedules, and diagnostics through natural conversation.4MIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server that lets AI assistants list and control home devices — lights, air conditioners, cameras, speakers, plugs and scheduled tasks — across Xiaomi (Mi Home), Tuya, Midea, eWeLink (Sonoff) and Huawei SmartHome using accounts you authorize on your own machine. It binds to localhost only and communicates with each vendor cloud, so agents can act on devices through natural language.27 npm2MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that wraps the Ambient Weather REST API. Query your personal weather stations conversationally from Claude Code, Claude.ai, or any MCP-compatible client.1MIT
- AlicenseAqualityDmaintenanceMCP server for controlling Wyze smart home devices (plugs, switches, thermostats, air purifiers) via Claude Desktop or Home Assistant.7MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables any AI agent to call Claude using your existing Max/Pro subscription via OAuth, avoiding additional API billing.11MIT
TDQS
Scored across 26 tools
Most tools target a distinct resource+action, and the descriptions carefully separate the subtle pairs (boost vs. set_temperature vs. set_mode, cancel_heating_boost vs. cancel_hot_water_boost). The weak spot is the inventory/state family: hive_list_devices, hive_list_smart_devices, hive_list_trvs, hive_get_heating and hive_get_overview all report overlapping device data (plugs, bulbs and sensors appear in both list tools), so an agent can plausibly pick the wrong listing tool.
Every tool uses the hive_ prefix plus a snake_case verb_noun form (hive_set_*, hive_get_*, hive_list_*, hive_boost_*, hive_cancel_*), which is predictable and readable. The only wobble is the interchangeable use of get_ and list_ for state-reading operations (hive_get_heating vs. hive_list_trvs) and boost_ acting as its own verb class.
26 tools is at the heavy end for a single-home control server; the surface is broad (heating, hot water, schedules, devices, lights, plugs, actions, holiday mode, auth) so most tools do earn their place. Even so, several near-duplicates (cancel_heating_boost/cancel_hot_water_boost, list_devices/list_smart_devices) suggest the set could be consolidated to roughly 18-20 entries.
Heating and hot water have full lifecycle coverage — read state, set mode, set temperature/target, boost, cancel boost, read and write schedules — plus holiday mode, device listing, lights, plugs, actions and an overview snapshot. Minor gaps remain: TRV calibration, mounting and child lock are only readable via hive_list_trvs with no setters, and there is no single-device detail lookup, but agents can work around these.