netatmo energy mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETATMO_MCP_WRITE | No | Kill switch. Set to 0 to force read-only mode, even with a write-enabled login. | |
| NETATMO_MCP_CONFIRM | No | Confirmation mode for write operations. Use 'elicitation' to allow changes only through a confirmation prompt shown by your client, or 'token' if your client cancels every change without showing anything. | |
| NETATMO_MCP_MAX_TEMP | No | Maximum allowed temperature in Celsius for manual setpoints. | 28 |
| NETATMO_MCP_MIN_TEMP | No | Minimum allowed temperature in Celsius for manual setpoints. | 7 |
| NETATMO_MCP_MAX_SETPOINT_HOURS | No | Maximum duration in hours for temporary manual setpoints. | 3 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| netatmo_get_heating_summaryA | Per-room temperature statistics, mean setpoint, time below / within / above target, largest temperature drop and cool-down rate, plus total boiler heat-demand time. Default: yesterday. Deterministic calculations; no energy or gas figures. |
| netatmo_compare_roomsA | Compare all rooms over a period (default: last 7 days): warmest/coolest, most variable, most time below target, largest drop and fastest cool-down after setpoint decreases. Returns per-room metrics and rankings. |
| netatmo_detect_anomaliesA | Rule-based detection of unusual readings in 30-minute room data (default: last 24 h, at most 14 days): implausible values or jumps, constant readings, missing data, rapid drops at a constant setpoint, sustained deviation from the setpoint. Each finding has severity, confidence, evidence and an explanation; findings are observations, not diagnoses. |
| netatmo_list_homesA | List the homes in the Netatmo account that have Energy devices (thermostats, radiator valves), with room and device counts and whether boiler history is available. |
| netatmo_get_homeA | Details of one home: heating mode, schedules, rooms and devices (topology only; use the status tools for live values). |
| netatmo_list_roomsA | List the rooms of a home with their IDs, types and the devices installed in each. |
| netatmo_list_devicesA | List thermostats, radiator valves and relays/gateways of a home with their model, room and gateway. Use netatmo_get_device_status for battery, signal and reachability. |
| netatmo_get_home_statusB | Current temperature, setpoint, mode and heating demand of every room, boiler on/off, and alerts (unreachable devices, low batteries, open windows). |
| netatmo_get_room_statusA | Current measured temperature and target temperature (setpoint) of one room, with setpoint mode, heating demand and open-window state. Identify the room by room_id or room_name. |
| netatmo_get_heating_statusA | Whether the boiler is currently requested to heat, which rooms request heat (heating demand %), and anticipation. Demand is not boiler power or energy use. |
| netatmo_get_device_statusA | Battery, radio/Wi-Fi signal, reachability, firmware and error codes of all devices of a home, or of one device. |
| netatmo_get_temperature_historyA | Measured temperature history of a room with statistics (min, max, mean, variability) and coverage/gaps. Default: last 24 h, aggregated. Missing data is reported, never filled in. |
| netatmo_get_setpoint_historyA | Target temperature (setpoint) history of a room, including the periods during which each setpoint applied. Default: last 24 h. |
| netatmo_get_boiler_historyA | How long the thermostat requested heat from the boiler over a period (minutes and share of time), per bucket. Requires a Netatmo thermostat. This is heat-demand time, not gas or energy consumption. Default: yesterday. |
| netatmo_get_schedulesA | Weekly heating schedules of a home: zones (e.g. Comfort, Night, Eco) with the setpoint of each room, away/frost-guard temperatures, and the timetable as day + time + zone. Shows which schedule is active. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| heating_daily_report | Summarise one day of heating: temperatures, setpoints and boiler activity. |
| heating_anomaly_review | Look for unusual temperatures, gaps or setpoint deviations over a period. |
| room_comparison | Compare temperatures and setpoint adherence across rooms. |
| heating_efficiency_review | Review heating patterns (setpoints, boiler demand time, overheating) for possible optimisation opportunities. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| homes | Homes with Netatmo Energy devices, with room/device counts. |
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.