Weishaupt WEM Portal
Monitor and control Weishaupt heating hardware through the WEM Portal from your agent for home lab or property ops automation.
Overview
Weishaupt WEM MCP Server is an MCP server for the Operate phase that controls and monitors Weishaupt heating systems via the WEM Portal API.
What is this MCP server?
- Connects to Weishaupt WEM Portal API for heat system monitoring and control
- stdio npm @disane-dev/weishaupt-wem-mcp-server v0.2.0 with npx runtime hint
- Credentials via WEM_USERNAME, WEM_PASSWORD, optional WEM_API_URL override
- Default portal URL https://www.wemportal.com/app documented in env schema
- Niche IoT bridge for builders automating home or small-site energy systems via MCP
- Server version 0.2.0
- npm package @disane-dev/weishaupt-wem-mcp-server
- stdio transport with npx runtimeHint
What problem does it solve?
Builders with Weishaupt heat systems want agent-driven status and control without bespoke scrapers or constant manual portal use.
Who is it for?
Solo devs or homelab operators who already use Weishaupt WEM and want MCP-native monitoring and control in their agent stack.
Skip if: Builders without Weishaupt/WEM hardware, multi-vendor smart-home orchestration needs, or teams requiring enterprise BMS features.
What do I get? / Deliverables
After you add portal credentials to MCP config, your agent can read and adjust heating through documented tools instead of one-off scripts.
- Agent-accessible heating status and control via WEM API
- Repeatable portal operations without custom UI automation
- Configurable portal base URL for non-default endpoints
Recommended MCP Servers
Journey fit
Heating system control is ongoing production operations—temperature, alarms, and adjustments—not a one-time build artifact. Monitoring subphase matches portal-backed telemetry and remote control of physical infra you keep running after integration work is done.
How it compares
Single-vendor heating portal MCP, not a universal IoT skill or cloud infra monitor.
Common Questions / FAQ
Who is weishaupt-wem-mcp-server for?
It is for developers and operators with Weishaupt heating tied to the WEM Portal who want Claude Code or Cursor to monitor and control their system.
When should I use weishaupt-wem-mcp-server?
Use it in Operate when you need ongoing temperature checks, alerts, or remote adjustments through an agent instead of the portal UI alone.
How do I add weishaupt-wem-mcp-server to my agent?
Register stdio MCP with npx @disane-dev/weishaupt-wem-mcp-server, set WEM_USERNAME and WEM_PASSWORD, optionally WEM_API_URL, then call the server tools from your agent.