weishaupt-wem-mcp-server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@weishaupt-wem-mcp-server show me an overview of my heating system"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Weishaupt WEM Portal MCP Server
Control and monitor your Weishaupt heating system with AI assistants via the WEM Portal
Features
Device Discovery - List all devices and modules from your WEM Portal account
Live Parameters - Read temperatures, pressure, operating modes with current values
Full Overview - Get a complete snapshot of your entire heating system in one call
Write Parameters - Adjust target temperatures, operating modes, schedules
Device Status - Check connection status of your devices
Writable Filter - List only the parameters you can actually change
Session Management - Automatic cookie-based auth with login lock for concurrent requests
Related MCP server: victron-tcp
Quick Start
Install via npx (recommended)
No installation needed. Configure your MCP client to run:
npx @disane-dev/weishaupt-wem-mcp-serverInstall from source
git clone https://github.com/Disane87/weishaupt-wem-mcp-server.git
cd weishaupt-wem-mcp-server
npm install
npm run buildConfiguration
Add to your Claude Desktop config:
Windows:
%APPDATA%\Claude\claude_desktop_config.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"weishaupt-wem": {
"command": "npx",
"args": ["-y", "@disane-dev/weishaupt-wem-mcp-server"],
"env": {
"WEM_USERNAME": "your_email@example.com",
"WEM_PASSWORD": "your_password"
}
}
}
}claude mcp add weishaupt-wem -- npx -y @disane-dev/weishaupt-wem-mcp-serverSet the environment variables WEM_USERNAME and WEM_PASSWORD before starting.
{
"mcpServers": {
"weishaupt-wem": {
"command": "node",
"args": ["/path/to/wem-mcp/build/index.js"],
"env": {
"WEM_USERNAME": "your_email@example.com",
"WEM_PASSWORD": "your_password"
}
}
}
}Environment Variables
Variable | Required | Description |
| Yes | Your WEM Portal email |
| Yes | Your WEM Portal password |
| No | API base URL (default: |
Available Tools
Tool | Description |
| List all devices with modules. Call this first to discover IDs. |
| Get connection status of a device |
| Full device overview: all modules with all parameters in one call |
| Get all parameters of a module with current values |
| Get parameter metadata (names, min/max, enums, writable flag) |
| List only adjustable parameters with ranges and options |
| Read specific parameter values by ID |
| Set a parameter value (e.g., target temperature) |
Start withwem_get_devices to discover your deviceId, moduleIndex, and moduleType, then use wem_get_overview for a complete snapshot of your heating system.
Typical Workflow
1. wem_get_devices
-> Returns devices with modules (WE0=heat generator, HZK0=heating circuit, WW0=hot water)
2. wem_get_overview (deviceId)
-> Returns ALL modules with ALL parameters in one call
3. wem_get_writable_parameters (deviceId, moduleIndex, moduleType)
-> Shows what you can adjust, with min/max ranges
4. wem_write_parameter (deviceId, moduleIndex, moduleType, parameterId, numericValue)
-> Sets a writable parameter (e.g. target temperature)Common Module Types
Type | Name | Description |
1 | SYSTEM | System overview |
2 | HZK | Heating circuit (temperatures, operating mode) |
3 | WW | Hot water (temperature, push, schedule) |
5 | TERMINAL | Control panel |
6 | GATEWAY | Communication gateway |
7 | WE | Heat generator (boiler/heat pump performance) |
9 | Device | Physical device unit |
10 | GROUND | Ground module |
Development
Command | Description |
| Build the project |
| Watch mode (auto-rebuild on changes) |
| Run server directly |
| Test API connection |
| Official MCP Inspector (Web UI) |
| CLI inspector for quick API tests |
Troubleshooting
Make sure you can log in atwemportal.com before using this server.
Issue | Solution |
Authentication failed | Verify credentials, check if WEM Portal blocks after too many attempts |
Connection timeout | Check internet, WEM Portal may be temporarily unavailable (30s default timeout) |
Parameter values show 0 | Some parameters (e.g. room temperature) require a physical sensor connected to the device |
Contributing
Contributions are welcome! Please open an issue or submit a pull request.
License
MIT - see LICENSE
disane.dev | Blog | GitHub | npm
Available Tools
8 toolswem_get_devicesA
Get all WEM devices with their modules. Returns device IDs, names, connection status, and module list (each with Index, Type, Name). Use this first to discover deviceId, moduleIndex, and moduleType needed for other tools.
Inputs: no named parameters.
wem_get_device_statusB
Get connection/online status of a specific device.
Inputs: deviceId (required).
wem_get_overviewA
Get a complete overview of a device: all modules with all their parameters and current values in a single call. Useful for getting a full picture of the heating system state.
Inputs: deviceId (required).
wem_get_parameter_metaA
Get metadata for all parameters of a module: parameter IDs, names, writable flag, data types, min/max values, enum options. Use this to discover available parameters before reading values.
Inputs: deviceId (required), moduleType (required), moduleIndex (required).
wem_get_parametersA
Get all parameters of a module with current values. Combines metadata + refresh + read into one call. Returns parameter names, current numeric/string values, units, and writable flags.
Inputs: deviceId (required), moduleType (required), moduleIndex (required).
wem_get_writable_parametersA
Get only the writable parameters of a module (parameters that can be changed). Shows current values, min/max ranges, and enum options. Useful to see what can be adjusted.
Inputs: deviceId (required), moduleType (required), moduleIndex (required).
wem_read_parametersA
Read current values for specific parameters. Refreshes data from device first, then reads. Use when you only need specific parameter values instead of all.
Inputs: deviceId (required), moduleType (required), moduleIndex (required), parameterIds (required).
wem_write_parameterA
Set a parameter value (e.g., target temperature). Only works for writable parameters. Check wem_get_parameter_meta for min/max values and enum options first.
Inputs: deviceId (required), moduleType (required), moduleIndex (required), parameterId (required), +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Five of eight tools are read-oriented and overlap substantially: wem_get_parameters explicitly 'combines metadata + refresh + read', which duplicates wem_get_parameter_meta and wem_read_parameters, while wem_get_overview and wem_get_writable_parameters are largely views/filters over the same data. The descriptions do clarify scope (device-wide vs module-wide vs specific params vs writable-only), preventing total confusion, but an agent must read carefully to pick correctly.
All tools use a clean wem_<verb>_<noun> snake_case pattern. The only blemish is inconsistent verb choice for the same operation: wem_get_parameters vs wem_read_parameters vs wem_get_parameter_meta, which mixes 'get' and 'read' for parameter retrieval.
Eight tools is a reasonable, well-scoped size for a device-control server. However, the read surface (overview, all parameters, specific parameters, writable parameters, metadata) could likely be consolidated to 2-3 tools, so a couple of tools do not fully earn their place.
The lifecycle is well covered: device discovery, status, parameter metadata, reading values, and writing values form a complete read/inspect/write loop. Minor gaps remain: no batch write for multiple parameters, and no alarm/fault/error diagnostics beyond connection status.
Maintenance
Related MCP Connectors
Home energy for AI assistants: live Power flow, Energy history, solar forecast, and device control.
Control your Tesla from your AI assistant - climate, charging, access, and security.
weclapp ERP in your AI assistant: reads instantly, writes only after a preview you approve.
- DNS-DATA RemoteDeprecatedcom.dns-data
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Home Assistant smart home devices through natural language. Control devices, manage automations, query entity states, and retrieve historical data across your home automation system.1MIT
- AlicenseAqualityBmaintenanceConnect AI assistants to Victron Energy systems to read real-time solar, battery, grid, and inverter data from your local network via Modbus TCP or MQTT.32134 npm7MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLM applications to query and visualize data from Bosch/Buderus heat pumps via ems-ESP, including temperatures, statistics, and heat curves through natural language.9MIT
- AlicenseAqualityDmaintenanceAn unofficial MCP (Model Context Protocol) server that exposes a Vaillant heat pump's data to AI assistants like Claude. Query outdoor and room temperatures, hot water status, energy consumption, COP estimates, schedules, and diagnostics through natural conversation.4MIT