A side-by-side look at the Netatmo Energy and Debmatic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Netatmo Energy for home automation work as a local process; choose Debmatic MCP for home automation as a local process. You can also run both side by side in one mcpServers block.
netatmo_list_homes, netatmo_get_home, netatmo_list_rooms.CCU_HOST, CCU_PASSWORD.Rows where the two servers differ are marked.
| Spec | N Netatmo Energy | |
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 55/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | other |
| Pricing | Free | Free |
| Required env vars | None listed | CCU_HOSTCCU_PASSWORD |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 9 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 21 | Not listed |
| Full listing | View Netatmo Energy | View Debmatic MCP |
netatmo_list_homesHomes with Energy devices, room/device countsnetatmo_get_homeHome details: heating mode, schedules, rooms, devicesnetatmo_list_roomsRooms with IDs, types and devicesnetatmo_list_devicesThermostats, valves, relays: model, room, gatewaynetatmo_get_home_statusCurrent status of every room, boiler state, alertsnetatmo_get_room_statusCurrent temperature and setpoint of one roomnetatmo_get_heating_statusBoiler on/off, rooms requesting heatnetatmo_get_device_statusBattery, signal, reachability, firmwarenetatmo_get_temperature_historyRoom temperature history with statistics and gapsnetatmo_get_setpoint_historyRoom setpoint history and setpoint periodsnetatmo_get_boiler_historyBoiler heat-demand time per hour/day/weeknetatmo_get_heating_summaryPer-room comfort metrics plus boiler time over a periodNo tool names declared yet. Check the project README from the listing page.
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"netatmo-energy": {
"command": "npx",
"args": [
"-y",
"netatmo-energy-mcp"
]
}
}
}
{
"mcpServers": {
"claymore666-debmatic-mcp": {
"command": "npx",
"args": [
"-y",
"ccu-mcp"
],
"env": {
"CCU_HOST": "YOUR_CCU_HOST_HERE",
"CCU_PASSWORD": "YOUR_CCU_PASSWORD_HERE"
}
}
}
}