MCP.Market

Weishaupt WEM Portal MCP server

by Disane87·io.github.Disane87/weishaupt-wem-mcp-server·v0.2.0

Control and monitor Weishaupt heating systems via the WEM Portal

B82/100grade B
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
New

0 stars55 downloads/wk

Reviews

Write one

Nobody has reviewed Weishaupt WEM Portal yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Weishaupt WEM Portal tools (8, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • wem_get_device_status

    Get connection/online status of a specific device.

  • wem_get_devices

    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.

  • wem_get_overview

    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.

  • wem_get_parameter_meta

    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.

  • wem_get_parameters

    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.

  • wem_get_writable_parameters

    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.

  • wem_read_parameters

    Read current values for specific parameters. Refreshes data from device first, then reads. Use when you only need specific parameter values instead of all.

  • wem_write_parameterwrite action

    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.

Public scan report

scanner v0.1.10 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 97 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Weishaupt WEM Portal compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
Tools
8
the typical server has 7
Tools that change things
13%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
55
more than 46% of 12,191 servers with a package

What its tools let an agent do: 7 read · 1 change

Install Weishaupt WEM Portal in Claude Code, Cursor or VS Code

Runs npx -y @disane-dev/weishaupt-wem-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add weishaupt-wem-mcp-server -- npx -y @disane-dev/weishaupt-wem-mcp-server
Add to Cursor

What the publisher says

From the Weishaupt WEM Portal repository's README, as published. We do not edit it. Read it on GitHub

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

Quick Start

Install via npx (recommended)

No installation needed. Configure your MCP client to run:

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

Install from source

git clone https://github.com/Disane87/weishaupt-wem-mcp-server.git
cd weishaupt-wem-mcp-server
npm install
npm run build

Configuration

Claude Desktop

Add to your Claude Desktop config:

  • Windows: %APPDATA%\Claude\claudedesktopconfig.json
  • macOS: ~/Library/Application Support/Claude/claudedesktopconfig.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 Code

claude mcp add weishaupt-wem -- npx -y @disane-dev/weishaupt-wem-mcp-server

Set the environment variables WEMUSERNAME and WEMPASSWORD before starting.

From source

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Weishaupt WEM Portal: common questions

Is Weishaupt WEM Portal MCP server safe?
Mostly: it is graded B (82/100). Read the Weishaupt WEM Portal safety report
How do I install Weishaupt WEM Portal?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Weishaupt WEM Portal need an API key?
No secret keys are declared. It reads 3 settings from the environment.
Is Weishaupt WEM Portal maintained?
The last commit was 135 days ago (2026-06-22). The latest release is v0.2.0.
How does Weishaupt WEM Portal compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.