Larnitech vs Plugwise MCP
A side-by-side look at the Larnitech and Plugwise MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Larnitech for home automation work as a local process; choose Plugwise MCP 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?
Choose Larnitech when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
Choose Plugwise MCP when
- You need dedicated capabilities in the Home Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
HUB1, HUB1IP, HUB2, HUB2IP, OPENAI_API_KEY, PLUGWISE_AGENT_MODEL. - You want tools like
add_hub, list_hubs, connect.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Home Automation | Home Automation |
| Quality signal | 40/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | HUB1HUB1IPHUB2HUB2IPOPENAI_API_KEYPLUGWISE_AGENT_MODEL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 2 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 16 |
| Full listing | View Larnitech | View Plugwise MCP |
Tools & capabilities
Larnitech tools
No tool names declared yet. Check the project README from the listing page.
Plugwise MCP tools 16
add_hubAdd a new Plugwise hub by providing its name (used as password). Scans the network to find the hub and stores it in the /hubs folder as a JSON file for future use. The hub name is the unique identifier printed on the back of your Plugwise device.list_hubsList all registered Plugwise hubs from the /hubs folder and in-memory registry. Returns hub information including name, IP address, model, and firmware version for each discovered hub.connectConnect to a Plugwise gateway (Adam, Anna, Smile P1, or Stretch) and retrieve gateway information. If no host is provided, automatically connects to the first discovered hub. Returns detailed gateway information including model, type, version, hostname, and MAC address.get_devicesRetrieve all Plugwise devices and their current states, sensors, and capabilities. Returns comprehensive information for all connected devices including thermostats, switches, sensors, and other appliances. Includes current readings, capabilities, and operational states.set_temperatureSet the temperature setpoint on a thermostat or zone. Supports single setpoint for heating/cooling systems, or separate low/high setpoints for heat pump systems. Changes take effect immediately.set_presetSet the preset mode on a thermostat or zone (e.g., home, away, sleep, vacation). Presets apply predefined temperature settings and behaviors configured in your Plugwise system.get_temperatureGet current room temperature and setpoint for a specific thermostat or zone. Returns both the measured temperature and the target setpoint.get_all_temperaturesGet current temperatures and setpoints for all thermostats and zones in the system. Returns comprehensive temperature data including measured values, setpoints, control states, and climate modes for every temperature-capable device.get_temperature_offsetGet the temperature offset (calibration) for a thermostat device. The offset is used to calibrate the temperature sensor if it reads incorrectly. Returns the current offset value and its valid range.set_temperature_offsetSet the temperature offset (calibration) for a thermostat device. This adjusts the measured temperature by a fixed offset.control_switchTurn a switch or relay on or off. Works with Plugwise switches, relays, and smart plugs. Use this to control any switchable device in your Plugwise network.set_gateway_modeSet the gateway mode (home, away, vacation). This is a system-wide setting that affects all zones and presets. Home mode uses normal schedules, away mode uses reduced temperatures, and vacation mode provides minimal heating/cooling.- +4 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.
Larnitech
{
"mcpServers": {
"larnitech": {
"command": "uvx",
"args": [
"larnitech-mcp"
]
}
}
}
Plugwise MCP
{
"mcpServers": {
"tommertom-plugwise-mcp": {
"command": "npx",
"args": [
"-y",
"plugwise-mcp-server"
],
"env": {
"HUB1": "YOUR_HUB1_HERE",
"HUB1IP": "YOUR_HUB1IP_HERE",
"HUB2": "YOUR_HUB2_HERE",
"HUB2IP": "YOUR_HUB2IP_HERE",
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"PLUGWISE_AGENT_MODEL": "YOUR_PLUGWISE_AGENT_MODEL_HERE"
}
}
}
}
Frequently asked questions
Larnitech is categorized under Home Automation and uses a local stdio subprocess. Plugwise MCP belongs to Home Automation and uses a local stdio subprocess. Pick Larnitech for home automation work and Plugwise MCP 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.
Larnitech has no declared pricing — check the project's own site. Plugwise MCP is listed as free. Auth: other. 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 larnitech and tommertom-plugwise-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Larnitech has a quality signal of 40/100 (Fair) with 2 views, 0 installs and 1 GitHub stars. Plugwise MCP has 57/100 (Good) with 3 views, 0 installs and 2 GitHub stars.