Netatmo Energy vs RokuMCP
A side-by-side look at the Netatmo Energy and RokuMCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
N
Netatmo EnergyHome Automation · Local subprocess (stdio)MCP server for Netatmo thermostats and radiator valves: status, history, analytics, opt-in control.55GoodAuth: oauth 2.0Verdict: choose Netatmo Energy for home automation work as a local process; choose RokuMCP for home automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
NChoose Netatmo Energy when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
netatmo_list_homes, netatmo_get_home, netatmo_list_rooms.
Choose RokuMCP when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ROKU_DEVICE_HOST, ROKU_DEVICE_PASSWORD. - You want tools like
roku_deploy, roku_delete_dev_channel, roku_discover.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N Netatmo Energy | |
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 55/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | ROKU_DEVICE_HOSTROKU_DEVICE_PASSWORD |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 21 | 38 |
| Full listing | View Netatmo Energy | View RokuMCP |
Tools & capabilities
Netatmo Energy tools 21
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 period- +9 more on the listing page
RokuMCP tools 38
roku_deploySideload (deploy) a Roku app to the deviceroku_delete_dev_channelDelete the currently sideloaded developer channelroku_discoverScan the local network for Roku devices via SSDProku_keypressSend a single key press (Home, Select, Up, Down, Left, Right, Back, etc.)roku_keypress_sequenceSend multiple key presses in sequence with configurable delayroku_type_textType a text string into the focused field (e.g. email, password, search)roku_launchLaunch or deep-link into a channelroku_query_device_infoGet device model, firmware, serial number, network inforoku_query_active_appGet the currently running approku_query_media_playerGet media player state (play/pause/buffer/stop), position, and durationroku_query_app_uiGet the current app UI tree as XMLroku_query_sg_nodesQuery SceneGraph nodes (all, roots, or by node ID)- +26 more on the listing page
Ready-to-paste client configs
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.
Netatmo Energy
{
"mcpServers": {
"netatmo-energy": {
"command": "npx",
"args": [
"-y",
"netatmo-energy-mcp"
]
}
}
}
RokuMCP
{
"mcpServers": {
"rokumcp": {
"command": "npx",
"args": [
"-y",
"roku-mcp"
],
"env": {
"ROKU_DEVICE_HOST": "YOUR_ROKU_DEVICE_HOST_HERE",
"ROKU_DEVICE_PASSWORD": "YOUR_ROKU_DEVICE_PASSWORD_HERE"
}
}
}
}
Frequently asked questions
Netatmo Energy is categorized under Home Automation and uses a local stdio subprocess. RokuMCP belongs to Home Automation and uses a local stdio subprocess. Pick Netatmo Energy for home automation work and RokuMCP for home automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Netatmo Energy is listed as free. Auth: oauth 2.0. RokuMCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add netatmo-energy and rokumcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Netatmo Energy has a quality signal of 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars. RokuMCP has 53/100 (Good) with 0 views, 0 installs and 3 GitHub stars.