netatmo energy mcp
Related Servers
Alternatives to netatmo energy mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceControl and monitor Weishaupt heating systems via the WEM Portal with AI assistants, enabling device discovery, parameter reading/writing, and system overview.865 npmMIT
- AlicenseAqualityAmaintenanceEnables AI assistants to control a Homey Pro smart home hub, create automation flows from natural language, and query device and energy history.3617 npmMIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that connects AI assistants to the ZONT heating system via the official REST API. It enables users to monitor device states, control heating modes, and perform diagnostics using natural language.MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to read live temperature, humidity, battery, offline status, alert definitions, and recent-reading summaries from WiFi sensors for freezers, fridges, and other monitored environments through a read-only API.531 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceSmart Device Control š® š” Lights: Brightness, color, RGB š”ļø Climate: Temperature, HVAC, humidity šŖ Covers: Position and tilt š Switches: On/off šØ Sensors: State monitoring Intelligent Organization š Grouping with context awareness. Robust Architecture š ļø Error handling, state validation ...79 npm58Apache 2.0
- AlicenseAqualityCmaintenanceConnects AI assistants to Loxone smart home systems for controlling devices, managing scenes, and monitoring real-time states through natural language. Supports lights, blinds, climate control, and automation with secure PIN-protected commands.3MIT
TDQS
Scored across 15 tools
Most tools have clearly distinct scopes, especially around homes, rooms, devices, histories, and schedules. However, netatmo_get_home_status and netatmo_get_heating_status overlap on boiler/heating-demand information, and netatmo_get_heating_summary overlaps with netatmo_compare_rooms and netatmo_get_boiler_history.
All tools consistently use the netatmo_ prefix plus snake_case verb_noun naming such as netatmo_list_rooms, netatmo_get_room_status, and netatmo_detect_anomalies. The pattern is predictable throughout the set.
Fifteen tools is well scoped for a heating/energy monitoring server, covering discovery, live status, history, schedules, and analytics without obvious padding. Each tool has a plausible role in the workflow.
The read-only monitoring surface is broad and covers discovery, status, history, schedules, and anomaly detection. However, there are no control operations for setting room setpoints, changing heating modes, editing schedules, or away/boost modes, which is a notable gap if energy management is in scope.