emsesp-mcp-server

bosch-buderus-wp/emsesp-mcp-server

3.3

If you are the rightful owner of emsesp-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

The EMS-ESP MCP Server integrates Bosch/Buderus heat pumps with LLM clients using the Model Context Protocol.

Tools

  1. statistics

    Provides statistical data related to heat pump performance.

  2. temperatures

    Offers temperature readings from various sensors.

  3. states

    Displays the current operational states of the heat pump.

  4. settings

    Shows the current configuration settings of the heat pump.

  5. pumps

    Provides information about the pump operations.

  6. eheater

    Displays data related to the electric heater component.

EMS-ESP MCP Server

MCP server for Bosch/Buderus heat pumps

📔 Table of Contents

🚀 About

With this Model Context Protocol (MCP) server, you can integrate your Bosch CS5800/6800i or Buderus WLW176/186i heat pump into a Large Language Model (LLM) client such as Claude Desktop.

This enables prompts like:

English:

  • Is hot water preparation running right now?
  • What is the current outdoor temperature?
  • How warm is the domestic hot water right now?
  • How much electricity is my heat pump currently using?
  • What is the current COP (Coefficient of Performance) for hot water preparation?

German:

  • Läuft gerade die Warmwasseraufbereitung?
  • Wie ist die aktuelle Außentemperatur?
  • Wie warm ist das Brauchwasser gerade?
  • Wie viel Strom benötigt meine Wärmepumpe im Moment?
  • Wie hoch ist meine Arbeitszahl der Warmwasseraufbereitung?

✍️ Integration in LLM Client

"emsesp": {
  "type": "stdio",
  "command": "npx",
  "args": [
    "-y",
    "tsx",
    "emsesp-mcp-server"
  ]
}

⚙️ Configuration

  • LOG_LEVEL (info): The log level of the logs which get written to ~/.emsesp-mcp/server-%DATE%.log
  • EMS_ESP_URL (http://ems-esp): Base URL of the EMS-ESP gateway
  • ENTITIES_CONFIG_PATH (./entities.json): Path to the entity configuration file
  • TAGS_AS_TOOLS (statistics,temperatures,states,settings,pumps,eheater): comma-separated list of tags. Each tag gets exposed as a separate tool. Each tool provides all entities which are tagged with the respective tag in the config file stored at ENTITIES_CONFIG_PATH.

🛠️ Available Tools

The MCP server in the current initial version provides read-only Tools which can be chosen by the LLM according to its needs. To reduce token size in the response and reduce irrelevant noise in the response, the huge list of entities provided by EMS-ESP has been reduced to a meaningful minimum and structured into groups with entities for similar categories like statistics or temperatures. To support the LLM in selecting the right tool and interpreting the response correctly - hopefully with as little hallucinations as possible, tools and the returned entities are well described.

Each entity of EMS-ESP has a list of tags in :

"dhw.nrg": {
      "title": "Total heat energy generated for hot water",
      "tags": ["statistics", "energy", "dhw", "prod-nrg"]
    },

All entities associated to a tag are exposed with the respective MCP tool.

If you want to add more entities, copy and add your additional entities. Then you can use the modified file in the MCP server via the environment variable ENTITIES_CONFIG_PATH=<path-to-modified-file>.

👓 Outlook

  • More entities
  • Tools to set room temperature, start desinfection, enable PV surplus, ...
  • Prompts to draw heat curve, etc.

📄 License