# Tommertom/plugwise-mcp [Health: Active]

**Category:** 🏠 Home Automation  
**Repository:** https://github.com/Tommertom/plugwise-mcp  
**GitHub Stars:** 2  
**npm Downloads (last month):** 95  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/tommertom-plugwise-mcp

## Description
TypeScript-based smart home automation server for Plugwise devices with automatic network discovery. Features comprehensive device control for thermostats, switches, smart plugs, energy monitoring, multi-hub management, and real-time climate/power consumption tracking via local network integration.

## Tools
Capabilities this server exposes over MCP:

- **add_hub** — Add 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_hubs** — List 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.
- **connect** — Connect 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_devices** — Retrieve 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_temperature** — Set 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_preset** — Set 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_temperature** — Get current room temperature and setpoint for a specific thermostat or zone. Returns both the measured temperature and the target setpoint.
- **get_all_temperatures** — Get 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_offset** — Get 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_offset** — Set the temperature offset (calibration) for a thermostat device. This adjusts the measured temperature by a fixed offset.
- **control_switch** — Turn 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_mode** — Set 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.
- **set_dhw_mode** — Set the domestic hot water (DHW) heating mode for systems with hot water control. Auto mode follows the schedule, boost mode provides immediate hot water heating, comfort mode maintains higher temperature, and off mode disables DHW heating.
- **set_regulation_mode** — Set the heating regulation mode. Controls the overall heating system behavior. Use "heating" for normal operation, "off" to disable heating, or bleeding modes for system maintenance.
- **delete_notification** — Delete the active notification from the Plugwise gateway. Use this to clear system notifications, alerts, or warnings displayed on the gateway.
- **reboot_gateway** — Reboot the Plugwise gateway (use with caution). This will restart the gateway, temporarily interrupting all control and monitoring. The gateway will be offline for 1-2 minutes. Only use when necessary for troubleshooting.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "plugwise-mcp": {
    "command": "npx",
    "args": ["-y","plugwise-mcp-server"],
    "env": {
      "HUB1": "",
      "HUB1IP": "",
      "HUB2": "",
      "HUB2IP": "",
      "OPENAI_API_KEY": "",
      "PLUGWISE_AGENT_MODEL": ""
    }
  }
}
```

**Requires environment variables:** `HUB1`, `HUB1IP`, `HUB2`, `HUB2IP`, `OPENAI_API_KEY`, `PLUGWISE_AGENT_MODEL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Tommertom/plugwise-mcp MCP server does

Tommertom/plugwise-mcp MCP server gives an MCP client access to Plugwise gateways and the devices connected to them. It supports Adam, Anna, Smile P1, and Stretch gateways and can manage more than one hub. The server can discover hubs on the local network, save discovered hub details in a `/hubs` folder, and reuse those registrations later.

Its device coverage includes thermostats, zones, switches, relays, smart plugs, sensors, and other appliances exposed by the Plugwise system. Read operations return gateway information, device states, sensor readings, capabilities, temperatures, setpoints, control states, and climate modes. A `plugwise://devices` resource provides the current state of all devices, and a `setup_guide` prompt provides setup instructions.

## How it works

The server communicates with Plugwise hardware through the local network. `add_hub` scans for a hub using the supplied name, which is the unique identifier printed on the device and is also used as its password. Registered hubs can be inspected with `list_hubs`, which reports details such as name, IP address, model, and firmware version.

`connect` opens a gateway connection and returns identifying information including its model, type, version, hostname, and MAC address. When no host is provided, it connects to the first discovered hub. The standard server exposes more than 15 specialized tools. An alternate agent mode provides a natural-language interface through a single tool, while JSON-RPC mode supports scripted requests.

## Setup and configuration

Tommertom/plugwise-mcp MCP server requires Node.js 17 or newer and npm or yarn, plus a supported Plugwise gateway. Install it globally with `npm install -g plugwise-mcp-server`, run it directly with `npx plugwise-mcp-server`, or build it from source with `npm install` followed by `npm run build`.

Provide hub credentials through the MCP client's `env` configuration or a `.env` file. `HUB1`, `HUB2`, and similar variables hold the eight-character hub codes; matching variables such as `HUB1IP` and `HUB2IP` can provide known addresses for faster discovery and loading. The README includes stdio configurations for Claude Desktop, Cline, Cursor, Visual Studio Code Copilot, and Windsurf Editor.

The server can also run in mock mode for read-only and feature tests without physical hardware. Agent mode can use `OPENAI_API_KEY` and `PLUGWISE_AGENT_MODEL` when configured with the natural-language agent.

## Tools and capabilities

- Discover and register hubs with `add_hub`, then list them with `list_hubs`.
- Connect to a selected gateway and retrieve gateway metadata.
- Read all devices, current states, sensors, capabilities, and measurements.
- Read one temperature or all temperatures and their setpoints.
- Set thermostat temperature setpoints, including separate low and high values for heat-pump systems.
- Change thermostat presets such as home, away, sleep, and vacation.
- Read or adjust thermostat temperature calibration offsets.
- Turn Plugwise switches, relays, and smart plugs on or off.
- Set gateway modes, domestic hot water modes, and heating regulation modes.
- Clear active gateway notifications or reboot a gateway.

## Limitations and notes

The server controls devices through the local Plugwise network, so the relevant gateway must be reachable and its credentials must be available. Gateway reboots interrupt monitoring and control for approximately one to two minutes and should be reserved for troubleshooting.

_Full upstream README: https://allmcps.com/mcp/tommertom-plugwise-mcp/readme_