Weishaupt WEM Portal

io.github.Disane87Published by GitHub account Disane87v0.2.0Updated Oct 27, 2026

Control and monitor Weishaupt heating systems via the WEM Portal

VerifiedSTDIODesktop onlyLocation & LifestyleProductivity & Workflow

Overview

AI-generated overview

Connects an assistant to a Weishaupt WEM Portal account to list heating devices, read live parameters and change writable settings.

What you can do
  • List devices and modules, and check device connection status
  • Read live parameters and metadata such as names, ranges, enums and writable flags
  • Get a full snapshot of all modules and parameters in one call
  • List only adjustable parameters with their ranges and options
  • Write parameter values such as target temperatures, operating modes and schedules
When to use it
Useful for owners of Weishaupt heating systems who want to inspect temperatures, pressure and operating modes, or adjust target temperatures and schedules, through an AI assistant instead of the WEM Portal web interface.
Requirements
Runs locally via npx (Node.js) or from a built source checkout. Requires a WEM Portal account with the WEM_USERNAME and WEM_PASSWORD environment variables set; WEM_API_URL is optional and defaults to the public portal. Needs internet access to the portal.
Before you install
The server stores your WEM Portal email and password in the MCP client configuration and logs in on your behalf. Write tools change real heating settings such as target temperatures and schedules, which can affect comfort, energy use or equipment; review changes before applying. Credentials are sent to the configured portal URL, so only change WEM_API_URL to a host you trust. Repeated failed logins may lock the account.

Installation

In SourceWeft

  1. Open Weishaupt WEM Portal in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[WEM Portal]

Weishaupt WEM Portal MCP Server

Control and monitor your Weishaupt heating system with AI assistants via the WEM Portal

[Version] [npm] [License: MIT] [Blog] [Website]

[MCP] [TypeScript] [Node.js] [semantic-release]

[GitHub Stars] [GitHub Issues] [CI]

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

Quick Start

Install via npx (recommended)

No installation needed. Configure your MCP client to run:

bash
npx @disane-dev/weishaupt-wem-mcp-server

Install from source

bash
git clone https://github.com/Disane87/weishaupt-wem-mcp-server.gitcd weishaupt-wem-mcp-servernpm installnpm run build

Configuration

Claude Desktop

Add to your Claude Desktop config:

  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
json
{  "mcpServers": {    "weishaupt-wem": {      "command": "npx",      "args": ["-y", "@disane-dev/weishaupt-wem-mcp-server"],      "env": {        "WEM_USERNAME": "[email protected]",        "WEM_PASSWORD": "your_password"      }    }  }}
Claude Code
bash
claude mcp add weishaupt-wem -- npx -y @disane-dev/weishaupt-wem-mcp-server

Set the environment variables WEM_USERNAME and WEM_PASSWORD before starting.

From source
json
{  "mcpServers": {    "weishaupt-wem": {      "command": "node",      "args": ["/path/to/wem-mcp/build/index.js"],      "env": {        "WEM_USERNAME": "[email protected]",        "WEM_PASSWORD": "your_password"      }    }  }}

Environment Variables

VariableRequiredDescription
WEM_USERNAMEYesYour WEM Portal email
WEM_PASSWORDYesYour WEM Portal password
WEM_API_URLNoAPI base URL (default: https://www.wemportal.com/app)

Available Tools

ToolDescription
wem_get_devicesList all devices with modules. Call this first to discover IDs.
wem_get_device_statusGet connection status of a device
wem_get_overviewFull device overview: all modules with all parameters in one call
wem_get_parametersGet all parameters of a module with current values
wem_get_parameter_metaGet parameter metadata (names, min/max, enums, writable flag)
wem_get_writable_parametersList only adjustable parameters with ranges and options
wem_read_parametersRead specific parameter values by ID
wem_write_parameterSet a parameter value (e.g., target temperature)

[!TIP] Start with wem_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

TypeNameDescription
1SYSTEMSystem overview
2HZKHeating circuit (temperatures, operating mode)
3WWHot water (temperature, push, schedule)
5TERMINALControl panel
6GATEWAYCommunication gateway
7WEHeat generator (boiler/heat pump performance)
9DevicePhysical device unit
10GROUNDGround module

Development

CommandDescription
npm run buildBuild the project
npm run watchWatch mode (auto-rebuild on changes)
npm startRun server directly
npm testTest API connection
npm run inspectorOfficial MCP Inspector (Web UI)
npm run inspector:cli -- devicesCLI inspector for quick API tests

Troubleshooting

[!NOTE] Make sure you can log in at wemportal.com before using this server.

IssueSolution
Authentication failedVerify credentials, check if WEM Portal blocks after too many attempts
Connection timeoutCheck internet, WEM Portal may be temporarily unavailable (30s default timeout)
Parameter values show 0Some 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

Made by me at Subthiel — software development & 3D printing

Source: README.md at commit 00f659c

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts